Skip to main content
Glama

create_skill

Create a tenant custom skill (runtime instructions agents can pin via skills[]). Use when encoding reusable domain guidance for agents. This is not an authoring guide; those are list_builder_guides / get_builder_guide. Authoring details are in get_builder_guide topic "skill".

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>",
      "name": "<name>",
      "description": "<description>",
      "body": "<body>"
    },
    "name": "create_skill"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesKebab-case ID (e.g. "my-skill")
bodyYesSkill instruction body (markdown)
nameYes
keywordsNo
descriptionYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare this is a non-destructive write (readOnlyHint=false, destructiveHint=false), so the safety profile is covered. The description adds useful context that the skill is tenant-scoped and consumable by agents via a skills[] reference. It does not disclose what happens on a duplicate id, whether id must be unique, or what the call returns, which matters for a creation mutation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the verb and resource, then usage, then the redirect. Nothing is repeated from the annotations or schema, and every sentence carries distinct routing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The pointer to get_builder_guide topic "skill" usefully offloads authoring detail, and no output schema exists to explain. However, for a tool with four required parameters at 40% coverage, the description leaves the payload semantics and likely failure mode (duplicate id) unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 40% — id and body are described, but name, description, and keywords are bare strings/arrays with no semantics anywhere. The description provides no parameter guidance at all, and with four required parameters an agent gets no explanation of how name relates to id or what keywords are used for.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Create a tenant custom skill") and immediately defines what a skill is — "runtime instructions agents can pin via skills[]" — which is information no sibling name reveals. It also explicitly disambiguates from list_builder_guides/get_builder_guide, so an agent can select it without opening another schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Use when encoding reusable domain guidance for agents" gives a positive trigger, and "This is not an authoring guide" plus the named alternative (get_builder_guide topic "skill") gives both an exclusion and a redirect. The only mild gap is no mention of update_skill for modifying an existing skill, but the routing to the right tool family is otherwise complete.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources