Skip to main content
Glama

Read a spec's listing

get_spec
Read-onlyIdempotent

Returns everything Spekkr knows about one spec: its manifest (what it builds, what the person may change under customize, the files, what it needs, the commands and secrets it uses under safety, the changelog). Read it before pull_spec to learn which choices the spec offers. Where the site has found specs like this one, related lists a few: each is another spec, with its own id to call get_spec with, and none of them is part of this one.

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

Input Schema

NameRequiredDescriptionDefault
idYesThe spec's id, like username/name.

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 establish read-only, idempotent, non-destructive, closed-world behavior, so the description focuses on what is actually returned: the full manifest with its named sections and a related-specs list with its own semantics. It does not mention size limits or truncation for large manifests, which is the only notable gap.

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?

The return contents are front-loaded and the pull_spec guidance follows immediately. The final sentence about 'related' is slightly convoluted in phrasing ('Where the site has found specs like this one, related lists a few') but earns its place by resolving a real ambiguity.

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

Completeness5/5

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

There is no output schema, so the description must carry the return shape, and it does — enumerating manifest sections and the related list with its meaning. Combined with the pre-pull_spec sequencing rule, an agent has everything needed to call and interpret this tool.

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?

With a single parameter at 100% schema description coverage, the schema already explains the id format ('username/name'). The description adds only indirect meaning — that related entries carry ids to pass back into get_spec — without refining the parameter's format or constraints, so this sits at the baseline.

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?

States a specific verb and resource ('Returns everything Spekkr knows about one spec') and immediately enumerates the manifest components it returns (builds, customize, files, needs, safety commands/secrets, changelog). This lets an agent distinguish it from get_spec_file and pull_spec without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Gives an explicit sequencing rule — 'Read it before pull_spec to learn which choices the spec offers' — which names the alternative and the condition that selects this tool. It also pre-empts a likely confusion by explaining that entries in 'related' are separate specs, not part of this one.

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