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

Input Schema

NameRequiredDescriptionDefault
taskYes
limitNo
explainNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose that results are ranked recommendations that can include 'weak matches', which is useful behavioral context not derivable from the schema. However, it says nothing about whether the call is read-only, how many results are returned, or what a 'weak match' means in practice.

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. The core purpose is front-loaded and the follow-up sentences are pure routing instructions, each earning its place.

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?

No annotations and no output schema mean the description alone must convey behavior, and it omits the `limit` parameter and any sense of the result shape (count, ordering, what a 'weak match' looks like). For a simple discovery tool this is adequate but visibly incomplete.

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%, so the description must compensate for three parameters. It explains `task` ('in plain words') and `explain` ('see matching terms and weak matches') but leaves `limit` entirely undefined — neither its meaning nor its default is stated. Two of three parameters are covered, so partial credit above the floor.

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 gives a concrete verb and resource: 'Find recommended installed skills for a task'. The qualifier 'in plain words' hints at natural-language input, and the closing sentence separates discovery here from retrieval via load_skill. It is clear without needing the sibling schema, though 'recommended' remains slightly abstract.

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?

Explicit routing is provided: use redirects the agent to `explain` for matching terms and weak matches, and to `load_skill` only for a recommended result. That establishes this as the discovery step in a two-step flow. It stops short of saying when this tool should not be used (e.g., already-known skill names).

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