Skip to main content
Glama

explain_issue

Explains an issue by returning its units, the claims recorded between them, and the record responsible for each claim.

Instructions

An issue with its units and every claim recorded between them, and which record made 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": {
      "issue_id": "<issue_id>"
    },
    "name": "explain_issue"
  }
}

Input Schema

NameRequiredDescriptionDefault
issue_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

D1.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it only hints at returned content (units, claims, originating record). It says nothing about whether the call is read-only, what permissions are needed, what happens with a bad issue_id, or how large the payload may be.

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

Conciseness2/5

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

It is a single short sentence, but that brevity is under-specification rather than conciseness: it is not front-loaded with an action and reads as a truncated clause with no clear subject or verb.

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?

An output schema exists, so return values needn't be re-explained, but for a tool with zero annotations and an undocumented required parameter the description should at minimum state the action and when to use it. Neither is present, leaving the definition inadequate.

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

Parameters1/5

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

Schema description coverage is 0% for the single required issue_id parameter, and the description never mentions the parameter or its expected format. The only hint ('which record made it') refers to the record's provenance, not to the input, so no meaning is added beyond the bare schema.

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

Purpose2/5

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

The text is a noun phrase fragment ('An issue with its units and every claim recorded between them...') rather than a verb+resource statement. It gestures at what the tool returns but never says what explain_issue actually does, and it does not distinguish the tool from siblings like describe, overview, or provenance.

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

Usage Guidelines1/5

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

There is no when-to-use guidance at all: no conditions, no prerequisites, no named alternatives. An agent cannot tell from this text whether to call explain_issue or the sibling describe/provenance tools for the same need.

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