Skip to main content
Glama

Check a spec before listing it

check_spec
Read-onlyIdempotent

Checks a spec someone is writing against Spekkr's listing rules and returns every problem at once. Pass the text of its spekkr.json. Nothing is saved or published. When it is ready, publish_spec publishes it.

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": {
      "manifest": "<manifest>"
    },
    "name": "check_spec"
  }
}

Input Schema

NameRequiredDescriptionDefault
manifestYesThe whole text of the spec's spekkr.json.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral detail – "Nothing is saved or published" and the all-at-once error reporting (rather than fail-fast) – but says nothing about the shape or volume of the returned problems.

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?

Four short sentences, front-loaded with the purpose and the input, then the side-effect disclaimer, then the routing hint to publish_spec. No filler or repetition.

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?

For a single-parameter validation tool with no output schema, the definition covers purpose, input form, side effects, and the next step in the workflow. Only the format of the returned problem list is left implicit, which is a minor gap.

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 coverage is 100% and the schema already says the parameter is the whole spekkr.json text. The description still adds useful meaning by phrasing it as "Pass the text of its spekkr.json," reinforcing that the raw content, not a path or ID, is expected – a distinction that matters given siblings like get_spec_file.

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 ("Checks a spec") plus the rule set it validates against ("Spekkr's listing rules") and the scope of the result ("returns every problem at once"). It also names the sibling it precedes, so an agent can distinguish it from publish_spec and get_spec without inspecting schemas.

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?

Clearly positions the tool as a pre-publication gate by naming publish_spec as the follow-up step ("When it is ready, publish_spec publishes it"). It gives a clear context for use, though it does not explicitly state when checking is unnecessary or whether it can be run repeatedly on drafts.

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