Skip to main content
Glama

show

Retrieve one strategy position by ID to view its Playing to Win box, adoption status, and recorded supporting, opposing, and complicating evidence.

Instructions

One position: its box, whether it is adopted, and the evidence noted on 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": {
      "position_id": "<position_id>"
    },
    "name": "show"
  }
}

Input Schema

NameRequiredDescriptionDefault
position_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the returned content at a high level but never states that this is a read-only operation, whether permissions are required, or what happens when the position is missing. Because an output schema exists, the field list is less additive than it appears.

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?

The description is a single compact sentence with no wasted preamble, but its noun-phrase structure is fragmentary and does not front-load an action clearly. It is concise without being well-structured for tool selection.

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?

The tool is simple, with one required parameter and an output schema, but the definition leaves key gaps: no read-only assurance, no missing-record behavior, and no parameter explanation. For a tool with zero annotation coverage and zero schema description coverage, this is under-specified.

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% for the single required parameter 'position_id', and the description never mentions it. The phrase 'One position' hints at an identifier but adds no meaning about format, source, or validation beyond the schema's bare integer type.

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 implies retrieving a single position by saying 'One position' and listing its fields, but it never uses an explicit verb like 'retrieve' or 'display'. The generic name 'show' plus fragmentary phrasing leaves the action somewhat vague, though the singular scope contrasts with the sibling 'list'.

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?

There is no guidance on when to use this tool versus alternatives such as 'list' or 'cascade_list'. The description does not state any preconditions, exclusions, or contextual triggers for selecting this tool.

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