MCP

MCP tool description template

A good MCP tool description tells an Agent what the Skill does, when to use it, required input, permission risk, and when to ask a human.

Find related SkillsRequest custom workflow

What this page helps with

It turns a broad AI automation idea into a searchable, comparable, reviewable Skill workflow.

  • Clarify the job to be done
  • Choose the right Skill category
  • Separate public inspection from authenticated runtime

What to inspect before adoption

Do not evaluate a Skill by name only. Inspect its manifest, input/output schema, permissions, publisher, review state, support path, and version history.

  • Start with free basics for low-risk work
  • Use project policy for customer data or internal systems
  • Submitted Skills remain inspection-only until verified

Recommended next step

Start in the marketplace, open the Skill detail page, compare permissions and examples, then sign in only when the Skill should become project state.

  • Browse the marketplace
  • Read docs and install path
  • Contact SkillHub for custom workflows

Keep reading

Template

Manifest review template

Use this template to check display name, description, version, runtime, input schema, output schema, permission notes, examples, support path, and changelog.

Workflow

SEO content brief workflow

This example shows how a team can move from keyword intent to page outline, citation gaps, FAQ, internal links, and implementation notes.

Publisher

Publisher launch checklist

A publisher can use this checklist before submitting a Skill for review: schema, runtime evidence, pricing intent, support path, and changelog must be clear.

MCP tool description template | SkillHub