Skip to main content
Glama

Pin one span

pin

write-time pinning: classify + hash-pin ONE span at write time

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": {
      "text": "<text>"
    },
    "name": "pin"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, i.e. a safe write, and 'write-time' largely restates that. Beyond it, the description says the tool classifies and hash-pins, but not what is stored, whether repeat calls are idempotent, or what happens if the span is already pinned.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short fragment with the key qualifier ('write-time', 'ONE span') front-loaded, so nothing is padded. But the terseness crosses into under-specification, giving the agent no detail to act on beyond a label.

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

Completeness2/5

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

For a single-parameter write tool with no output schema, the definition should say what is persisted, what the return looks like, and how it relates to sibling operations like snapshot. None of that is present, so an agent cannot confidently invoke it without inspecting other tools or trial and error.

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?

The schema documents zero of the one parameter, so the description must compensate and does not: 'text' is never explained – whether it is raw span content, a serialized span, or an identifier. The agent is left guessing what to pass, since 0% coverage leaves no fallback in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a concrete verb phrase ('classify + hash-pin') and scope ('ONE span at write time'), so the agent knows this pins a single span rather than many. However, 'hash-pin' and 'classify' are undefined jargon, and nothing distinguishes it from siblings audit, reinject, or snapshot, which could plausibly also touch spans.

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

Usage Guidelines2/5

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

'at write time' hints at the calling context (inside a write path), but there is no explicit when-to-use, when-not-to-use, or alternative such as reinject or snapshot. The agent must infer the workflow position from the word 'write-time' alone.

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