Skip to main content
Glama
Sign In
FTC Toolchain

FTC Toolchain

by Sanjit-K
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get FTC sample OpMode source

get_sample

Obtain the complete Java source of any official FTC sample OpMode by name. Use this to access sample code directly from the FTC SDK.

Instructions

Return the full Java source of an official FTC sample OpMode by name (from list_samples).

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

Input Schema

NameRequiredDescriptionDefault
nameYesSample name, e.g. BasicOmniOpMode_Linear

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It indicates a read operation but does not mention side effects, permissions, error handling, or what happens on invalid input. Lacks depth for a tool with no annotations.

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?

One sentence, no redundancy, front-loaded with key information. Every word serves a purpose.

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?

Given the tool's simplicity (1 param, no output schema, no annotations), the description covers the essential purpose and usage. It does not mention return format or errors, but for a straightforward retrieval tool it is sufficiently 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?

Schema coverage is 100% but the description adds value by linking the parameter to list_samples and providing an example. This goes beyond the schema description which only gives an example without the relational context.

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?

Description clearly states the verb 'return', the resource 'full Java source of an official FTC sample OpMode', and specifies the source of names 'by name (from list_samples)'. It distinguishes itself from siblings like list_samples and other tools.

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

Usage Guidelines3/5

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

The description mentions 'from list_samples' implying a prerequisite step, but does not explicitly state when to use this tool versus alternatives or provide exclusions. Given the number of siblings, more guidance would be beneficial.

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