Skip to main content
Glama
Sign In
FTC Toolchain

FTC Toolchain

by Sanjit-K
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Deploy code to robot

deploy

Install the built TeamCode APK on the connected robot and restart the Robot Controller app to apply code changes immediately.

Instructions

Install the built TeamCode APK on the connected robot (adb install) and restart the Robot Controller app. Run build first, and adb_connect/adb_devices to make sure a device is attached.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "deploy"
  }
}

Input Schema

NameRequiredDescriptionDefault
serialNoadb device serial if multiple devices are connected
projectPathNoPath to the FtcRobotController SDK project. Defaults to $FTC_TOOLCHAIN_PROJECT_DIR, then the workspace clone made by create_project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.9/5.0
Behavior5/5

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

No annotations are provided, but the description fully discloses the tool's actions (adb install, restart app) and requisite conditions, making behavior transparent.

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 sentences, no wasted words. Action is front-loaded: 'Install the built TeamCode APK...'.

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?

Given no output schema, the description sufficiently covers prerequisites and actions for a deploy tool, fully answering what the agent needs to know.

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 has 100% coverage so baseline is 3. Description adds value by explaining default for projectPath (env var or workspace clone), which goes beyond schema.

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 tool installs the built TeamCode APK and restarts the Robot Controller app. It distinguishes from siblings like build_and_deploy by explicitly requiring a prior build step.

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 advises to 'Run build first' and 'adb_connect/adb_devices to make sure a device is attached', providing clear when-to-use and prerequisites.

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