Skip to main content
Glama

MilliTool

recommend_skills

Read-onlyIdempotent

Find skills for a task or technology stack. Returns ranked candidates, indexed source commits, compatibility hints and installation suggestions. Does not install or run code.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
categoryNo
minSafetyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower, and the description still contributes the return shape: ranked candidates, indexed source commits, compatibility hints and installation suggestions. The explicit "Does not install or run code" reinforces the read-only contract rather than contradicting it. It stops short of describing ranking logic or result volume, which would have been the last useful detail.

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?

Two sentences with zero padding; the capability statement is front-loaded and the return summary plus boundary note follow in order of importance. Nothing restates the tool name or title.

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?

Purpose, return payload and action boundary are covered, which is adequate for a simple read-only search with no output schema. The gap is the undocumented filter parameters, especially minSafety, which an agent cannot use correctly from the definition alone.

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 carry all parameter meaning, and it does not. It hints at the query concept ("task or technology stack") but says nothing about limit, category, or minSafety — the latter being a 0-5 numeric threshold whose semantics are entirely opaque without explanation.

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?

Specific verb plus resource plus scope: "Find skills for a task or technology stack." An agent can distinguish it from get_skill_content or list_sources because this one returns ranked candidates rather than a single item or a source list. It never names a sibling explicitly, so differentiation is inferential 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 Guidelines3/5

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

The phrase "for a task or technology stack" implies the retrieval scenario, and "Does not install or run code" sets a boundary on downstream actions. However, there is no explicit when-to-use/when-not guidance and no routing to get_skill_content for reading a chosen skill's contents, leaving the agent to infer the follow-up step.

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