Skip to main content
Glama

ProofTask public

getTemplate

Read-onlyIdempotent

[No connection needed] Read one exact public template version returned by findTemplates. Use its criteria as a starting point for prepareAgreement after the user reviews them.

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": {
      "slug": "<slug>",
      "version": "<version>"
    },
    "name": "getTemplate"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes
versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, and non-destructive behavior, so the bar is lower. The description still contributes real context by noting no connection is required (auth/availability) and by framing this as a human-in-the-loop step before prepareAgreement. It does not discuss failure behavior for unknown slug/version pairs.

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?

Two short sentences, front-loaded with the availability hint and the core action, with the workflow hint second. The bracketed "[No connection needed]" prefix is slightly awkward stylistically but carries useful signal, and there is no filler.

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 two-parameter read tool with full annotations and no output schema, the behavioral picture is nearly complete. The gap is parameter documentation: with 0% schema coverage, an agent could still misconstruct the slug or pass a nonexistent version, and nothing here guards against that.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry the burden for both required parameters, and it does not. It implies slug/version come from findTemplates output but never explains the slug format constraint, that version is a positive integer, or that both are strictly required.

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 ("Read one exact public template version") with scope qualifiers (exact, public, single). The phrase "returned by findTemplates" also anchors it against the sibling that lists templates, so an agent can distinguish the two without opening either schema.

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?

Gives a clear downstream context: pull the criteria here, then use them as a starting point for prepareAgreement after the user reviews. The upstream dependency on findTemplates is explicit. It stops short of stating exclusion conditions (e.g., what to do if the version doesn't exist or the template is private).

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