Skip to main content
Glama

Pull a spec to build from

pull_spec
Read-onlyIdempotent

Returns a spec's files, ready to write into a folder and build from: BUILD.md (how to build), spekkr.json (the manifest), spekkr.inputs.json (the person's choices) and the spec files. It checks the choices first and refuses a key the spec does not declare or a value it does not offer. Anything not chosen keeps the spec's default.

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

Input Schema

NameRequiredDescriptionDefault
idYesThe spec's id, like username/name.
choicesNoThe person's choices, by key from manifest.customize: any text for a setting, true or false for an option (on and off are taken too), one of its choices for a swap. For example {"database": "sqlite", "teams": false}. The answer and spekkr.inputs.json write an option as true or false, as the manifest writes its default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare this as a read-only, idempotent, non-destructive, closed-world operation, so the safety profile is covered. The description adds real value beyond that: it discloses upfront validation (it refuses undeclared keys or unoffered values) and default-fallback semantics for omitted choices, both of which change how an agent prepares inputs.

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?

Three compact sentences, front-loaded with what is returned. Slight clutter in the nested asides about how options are written, and the phrase "the person's choices" is a bit informal, but nothing is wasted.

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 read-only, two-parameter tool whose safety profile is fully covered by annotations, the description covers the main gaps: what files come back, that choices are validated, and that defaults apply. Since there is no output schema, more detail on the envelope/format of the returned files would have been welcome, but the essential calling contract is clear.

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 coverage is 100%, so the id format and the choices object shape (text/boolean/integer values, true-false encoding) are already documented in the schema; the description largely restates them. It does add one semantic not in the schema — that anything not chosen keeps the spec's default — which is genuinely useful, but the remaining content overlaps the schema.

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 opens with a specific verb and resource ("Returns a spec's files") and enumerates the exact artifacts produced: BUILD.md, spekkr.json, spekkr.inputs.json and the spec files. It also frames the scope as "ready to write into a folder and build from." It stops short of naming how this differs from siblings like get_spec or get_spec_file, which return presumably different shapes.

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?

Usage is implied rather than stated: the tool is for the build workflow ("ready to write into a folder and build from"), and choices are pre-validated. There is no explicit when-to-use/when-not-to-use guidance and no named alternative for retrieving a single spec file or for checking a spec without pulling it.

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