Skip to main content
Glama
Sign In
AIWorkhub

AIWorkhub

by shrec
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

roadmap_show

Read-only

Retrieve one roadmap outcome by ID to view its stored fields. Use it when you know the outcome ID; for finding IDs or viewing linked tasks, use the list or snapshot tools.

Instructions

Show one Roadmap outcome.

Use this for one outcome's stored fields by id; use roadmap_list to find ids or roadmap_snapshot for every outcome joined to its linked tasks.

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": {
      "roadmap_id": "<roadmap_id>"
    },
    "name": "roadmap_show"
  }
}

Input Schema

NameRequiredDescriptionDefault
roadmap_idYesRoadmap outcome id in the form RM-YYYY-NNNNN, e.g. RM-2026-00001.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.12.67
    • addedInput schema / properties / roadmap_id / description
      Added value: +"Roadmap outcome id in the form RM-YYYY-NNNNN, e.g. RM-2026-00001."
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds the meaningful behavioral distinction that this returns only "stored fields" — i.e. no joined task data, unlike roadmap_snapshot — and that lookup is keyed by id rather than by query. It does not mention error behavior for an unknown id, which keeps it below a 5.

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

Conciseness5/5

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

Two short sentences with no filler. The core purpose is front-loaded and the disambiguation against siblings follows immediately, which is exactly the right order for an agent scanning definitions.

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

Completeness4/5

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

For a single-parameter read tool with full schema coverage and no output schema, the description supplies what matters: scope (one outcome), the field set (stored fields, not joined data), and routing to alternatives. A brief note on what an unknown id returns would make it fully complete.

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?

Schema coverage is 100% and the roadmap_id property already documents the RM-YYYY-NNNNN format with an example. The description only reinforces that lookup is by id. Baseline 3 is correct since the schema carries the parameter detail.

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?

"Show one Roadmap outcome" names a specific verb and resource, and the second sentence distinguishes it from roadmap_list (id discovery) and roadmap_snapshot (joined task data). An agent can pick it out of a large sibling set without opening any schema.

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

Usage Guidelines5/5

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

Explicitly states when to use this tool (one outcome's stored fields by id) and names both alternatives with the condition that selects each: roadmap_list to find ids, roadmap_snapshot for outcomes joined to tasks. Routing is fully resolved.

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