Skip to main content
Glama
Sign In
FTC Toolchain

FTC Toolchain

by Sanjit-K
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get Pedro Pathing doc page

get_doc

Retrieve a Pedro Pathing documentation page as markdown by specifying its document ID. Get the exact technical reference needed for FTC robot pathing.

Instructions

Return a full Pedro Pathing documentation page as markdown, by id from search_docs (e.g. 'pathing/examples/auto').

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": {
      "id": "<id>"
    },
    "name": "get_doc"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesDoc id, e.g. pathing/tuning/localization/pinpoint

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses the output format (markdown) and source (search_docs). It does not mention side effects or auth, but for a read-only retrieval tool, this is adequate.

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?

The description is a single sentence front-loaded with the verb and resource, no wasted words.

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

Completeness5/5

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

Despite no output schema, the description covers return type (markdown), source (search_docs), and parameter example. For a simple retrieval tool with one parameter, it is complete.

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

Parameters4/5

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

The schema describes 'id' as 'Doc id, e.g. pathing/tuning/localization/pinpoint' and the description adds an example 'pathing/examples/auto', reinforcing the format. With 100% schema coverage, the description adds extra value.

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?

The description clearly states the verb 'Return' and the resource 'full Pedro Pathing documentation page as markdown'. It specifies the input 'id from search_docs' and gives an example, distinguishing it from siblings like search_docs which lists ids.

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?

The description indicates that the id comes from search_docs, implying a prerequisite. It does not explicitly exclude alternatives or state when not to use, but the context is clear.

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