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

Input Schema

NameRequiredDescriptionDefault
idYes
revisionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / properties / revision
      Added value: +{
      +  "type": "string"
      +}
  2. Added

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. 'Load' implies a read-only fetch and the return contents are disclosed, but nothing is said about error behavior for an unknown id, size or truncation limits on the skill text, or whether loading has any side effects.

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 action, then the prerequisite, then the return shape. No filler or redundancy.

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

Completeness4/5

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

For a simple two-parameter loader with no output schema, the description covers purpose, id sourcing, and return fields, which is most of what an agent needs. The undocumented 'revision' parameter and absent failure-mode guidance are the remaining gaps.

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%, so the description must compensate. It explains 'id' well by tying it to find_skills output, but the second parameter, 'revision', is never mentioned — an agent cannot tell whether it pins a version, defaults to latest, or what format it accepts.

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', and adds what comes back (skill text, source, file list). That output list implicitly separates it from margrave_read_skill_file (a single file within a skill) and margrave_find_skills (discovery), though neither sibling is named explicitly.

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 an id from find_skills' gives a concrete prerequisite and routes the agent to the discovery tool first, which is the key sequencing decision. It stops short of stating when not to use it, e.g. that fetching individual files should go through margrave_read_skill_file instead.

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