Skip to main content
Glama
Sign In

Geppetto Robot Directory

by com.geppettorobotdirectory
OverviewDiscussionsAdmin

Get Robot Details

get_robot
Read-onlyIdempotent

Get full specs and details for a specific robot by its slug. Returns all specifications, price, brand, description, features, and direct URL.

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

Input Schema

NameRequiredDescriptionDefault
slugYesRobot slug e.g. agility-robotics-digit, roborock-s8-maxv-ultra, unitree-g1

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / slug / description
      Previous value: -"Robot slug e.g. agility-robotics-digit, roborock-s8-maxv-ultra, boston-dynamics-spot"New value: +"Robot slug e.g. agility-robotics-digit, roborock-s8-maxv-ultra, unitree-g1"
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive behavior. The description adds valuable behavioral context by listing what is returned, including specs, price, brand, description, features, and direct URL, which compensates for the absent output schema. It does not mention behavior when the slug is not found, but that is a minor gap given the annotation coverage.

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 two sentences with zero waste. It front-loads the action and resource, then summarizes return contents.

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?

This is a simple single-parameter read tool, and the description covers the return contents despite there being no output schema. Annotations handle safety and idempotency, so the definition is largely complete, though it could mention error behavior for an invalid slug.

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?

The schema already describes the slug parameter at 100% coverage with concrete example values. The description adds no meaning beyond restating that the slug identifies a specific robot, so the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: get full specs and details for a specific robot by slug. It implicitly distinguishes itself from search_robots by requiring a known slug, though it does not name sibling alternatives explicitly.

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?

Usage is implied by 'by its slug,' meaning the tool should be called when the slug is already known. The description does not state when to use this instead of search_robots for discovery, nor does it mention exclusions or alternatives.

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

All Geppetto Robot Directory toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources