Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

get_manual_revision

Read-only

Fetch a specific manual revision by its ID to review earlier assembly instructions or compare versions from Kiln's version history.

Instructions

Fetch a single manual revision by id.

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": {
      "manual_id": "<manual_id>"
    },
    "name": "get_manual_revision"
  }
}

Input Schema

NameRequiredDescriptionDefault
manual_idYesThe manual revision to fetch, as ``list_manual_history`` or ``generate_assembly_manual`` returned it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.1
    • addedInput schema / properties / manual_id / description
      Added value: +"The manual revision to fetch, as ``list_manual_history`` or ``generate_assembly_manual`` returned it."
  2. Addedv1.5.0

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered structurally. The description adds nothing beyond that: it does not say what error occurs for an unknown id, whether revisions are immutable, or what content a revision payload includes.

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?

One short sentence with no filler and the operation front-loaded. It is lean almost to a fault: nothing is wasted, but nothing is elaborated either.

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?

For a simple one-parameter read tool with no output schema, the description covers the core operation and annotations cover its safety profile. It remains silent on what a revision object contains and how failures manifest, which an agent would need to interpret results correctly.

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 that manual_id is a revision id as returned by list_manual_history or generate_assembly_manual. The description's phrase 'by id' repeats this without adding format, validation, or sourcing detail, so the baseline 3 applies.

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 names a specific verb and resource: fetch a single manual revision. 'Single' contrasts implicitly with collection tools. However, it does not distinguish itself from close siblings such as list_manual_history, retire_manual_revision, or diff_assembly_manuals, which an agent could easily confuse with it.

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 only implied: the agent is fetching an already-known revision rather than listing or generating one. There is no explicit when-to-use statement, no exclusion of the sibling tools, and no mention of where the id comes from, even though list_manual_history and generate_assembly_manual are named in the schema rather than the description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools