Skip to main content
Glama

orchestkit_skill_get

Read-onlyIdempotent

Show one OrchestKit skill as a card: what it does, which plugin ships it (ork or ork-extras), and the Claude Code install line. Use when a person asks about a skill by name. Input: the skill name, e.g. 'brainstorm'. An unknown name returns a 'no such skill' card with the nearest names.

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": {
      "name": "<name>"
    },
    "name": "orchestkit_skill_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesSkill name, e.g. brainstorm. A leading / or ork: is fine.

Output Schema

NameRequiredDescriptionDefault
nameNo
foundYes
queryNo
invokeNo
pluginNo
docsUrlNo
summaryNo
useWhenNo
versionNo
browseUrlNo
descriptionNo
suggestionsNo
installCommandNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuine behavioral context beyond that: the shape of the returned card and the failure path ('An unknown name returns a no such skill card with the nearest names'), which is exactly the kind of edge case an agent needs before calling.

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 what the tool returns, followed by the usage trigger and the input/error contract. Nothing is redundant with the annotations and no sentence could be dropped without losing information.

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

Completeness5/5

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

For a single-parameter read tool with an output schema and full annotation coverage, the description covers the remaining gaps: when to reach for it, what the payload means, and how unknown input is handled. An agent has everything needed to select and invoke it correctly.

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

Parameters3/5

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

With one required parameter at 100% schema description coverage, the schema already documents the name argument and its accepted forms. The description restates the same example ('brainstorm') and the leading '/' or 'ork:' tolerance, adding essentially no meaning beyond the schema, so baseline 3 applies.

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

Purpose4/5

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

States a specific verb and resource ('Show one OrchestKit skill') and enumerates what the returned card contains (behavior, shipping plugin, install line), which makes the tool's job concrete. It implicitly separates itself from the docs/install siblings by being a per-skill lookup, but never names them, so differentiation is inferred rather than stated.

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

Usage Guidelines4/5

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

'Use when a person asks about a skill by name' gives a clear triggering condition, which is the main routing question for this tool. There is no explicit when-not clause or pointer to orchestkit_docs_search / orchestkit_docs_get for adjacent queries, so the guidance is clear but not exhaustive.

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.