Skip to main content
Glama

margrave_find_skills

Find recommended installed skills for a task in plain words. Use explain to see matching terms and weak matches. Use load_skill only for a recommended result.

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

Input Schema

NameRequiredDescriptionDefault
taskYes
limitNo
explainNo

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 / explain
      Added value: +{
      +  "type": "boolean"
      +}
  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, and it discloses one real behavioral constraint: loading is reserved for results this tool recommends. It says nothing about what a result contains, ordering/ranking, default result count, or whether searching has 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.

Conciseness4/5

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

Three short sentences with the core purpose front-loaded and no filler. The routing sentences are compact, though the phrase 'in plain words' is slightly informal for a parameter constraint.

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?

With no output schema and no annotations, the description should say more about what a returned 'skill' looks like and how recommendations are ordered or limited. The load_skill pointer implies results carry usable identifiers, but an agent must infer the rest.

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?

Schema description coverage is 0%, and the description explains two of three parameters: 'task' is implicitly natural-language ('in plain words') and 'explain' is defined by its effect. The 'limit' parameter, including its default and accepted range, is left entirely undocumented.

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?

The description uses a specific verb and resource ('Find recommended installed skills for a task') and constrains the input to plain words, which is clearer than a bare name restatement. It does not, however, sharply contrast itself with sibling margrave_load_skill beyond a one-line routing note.

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?

It gives actionable guidance for the 'explain' parameter ('to see matching terms and weak matches') and an explicit conditional for the sibling ('Use load_skill only for a recommended result'). It stops short of saying when not to use this tool at all, or what to do when nothing matches.

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