Skip to main content
Glama

Margrave

load_skill

Load the instructions of one skill. Use an id from find_skills. Returns the skill text, its source, and its file list.

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": "load_skill"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
revisionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. It does add useful output context (returns skill text, source, and file list), which compensates for the absent output schema, but says nothing about idempotency, error behavior for unknown ids, or what the optional revision does. For a read tool with zero annotation coverage this is adequate but thin.

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 with zero filler, front-loaded with the action and then the input source and return shape. Every sentence adds distinct 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?

Covers the return payload well enough to substitute for the missing output schema, and explains id sourcing. However the revision parameter and the read_skill_file alternative are unaddressed, leaving an agent without enough to call it correctly in ambiguous cases.

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 description coverage is 0% with two parameters, so the description must carry the meaning. It meaningfully explains where id comes from (find_skills), but the revision parameter is never mentioned, leaving half the parameters undocumented in both schema and description.

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: "Load the instructions of one skill." This clearly separates retrieval from discovery by pointing to find_skills for the id, though the sibling read_skill_file is never differentiated, leaving some ambiguity about which tool reads skill content.

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?

Gives a concrete prerequisite — the id must come from find_skills — which tells the agent where this tool fits in a workflow. It stops short of stating when NOT to use it, particularly versus read_skill_file, so the boundary between loading instructions and reading a file is left to inference.

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