Skip to main content
Glama

MilliTool

get_skill_content

Read-onlyIdempotent

Get indexed metadata and content preview for a skill_id returned by recommend_skills. Includes pinned source URL and install suggestion; preview may be incomplete. Does not fetch arbitrary URLs or execute 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": {
      "skill_id": "<skill_id>"
    },
    "name": "get_skill_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
skill_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds value beyond that by disclosing what comes back (metadata, content preview, pinned source URL, install suggestion) and by warning that the preview may be incomplete. It does not cover failure behavior for an invalid or stale skill_id, which keeps it from a 5.

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: purpose first, return contents second, exclusions last. Every clause carries information an agent would otherwise have to guess, and there is no restatement of the tool name or filler.

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?

With no output schema, the description carries the burden of describing the return value, and it does so adequately by naming the metadata, preview, source URL, and install suggestion plus the incompleteness caveat. The remaining gap is error or not-found behavior for an invalid skill_id, which is a secondary concern for a read-only lookup.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the single skill_id parameter carries no documentation in the schema itself. The description compensates by stating the parameter's provenance (an ID returned by recommend_skills) and by ruling out arbitrary URLs as input, which is meaningfully more than the bare string type and maxLength constraint.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource (get indexed metadata and content preview) and scopes the input to a skill_id returned by recommend_skills, which immediately distinguishes it from the recommendation sibling. The closing sentence rules out two plausible misreadings (arbitrary URL fetching and code execution), so an agent can tell exactly what this tool is not.

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?

The phrase 'for a skill_id returned by recommend_skills' establishes the intended workflow and the upstream tool that produces valid input, which is real when-to-use guidance. It lacks an explicit exclusion against browse_categories or list_sources, but the negative sentence about URL fetching and code execution covers the main misuse cases.

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