Skip to main content
Glama

BRAINIAC Industrial Robotics & Automation Intelligence

Diff ROS topic schemas

robotics-intelligence_ros-topic-schema-diff
Read-onlyIdempotent

Compare caller-supplied left/right ROS topic message types and fields. Missing schemas are not invented. Price $0.03 USDC. POST /api/v1/robotics-intelligence/ros-topic-schema-diff. An unpaid call returns the x402 payment terms and does not run.

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": "robotics-intelligence_ros-topic-schema-diff"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNocsv, string, length 0 to 200000. Optional.
asOfNoasOf, string, length 0 to 40. Optional.
fileNofile, object. Optional.
jsonNojson, string, length 0 to 200000. Optional.
textNotext, string, length 0 to 200000. Optional.
filesNofiles, array. Optional.
cyclesNocycles, array. Optional.
samplesNosamples, array. Optional.
schemasNoschemas, array. Optional.
downtimeNodowntime, array. Optional.
opcuaTagsNoopcuaTags, array. Optional.
plcAlarmsNoplcAlarms, array. Optional.
protocolsNoprotocols, array. Optional.
maintenanceNomaintenance, array. Optional.

Output Schema

NameRequiredDescriptionDefault
itemsNoitems. Array.
statusNostatus. String.
findingsNofindings. Array.
checkedAtNocheckedAt. String.
topicCountNotopicCount. Number.
limitationsNolimitations. Array.
apiKeyRequiredNoapiKeyRequired. Boolean.
paidProviderUsedNopaidProviderUsed. Boolean.
machineCommandsIssuedNomachineCommandsIssued. Boolean.
liveEquipmentConnectedNoliveEquipmentConnected. Boolean.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the bar is lower. The description adds genuinely non-obvious behavior: a $0.03 USDC price, x402 gating where unpaid calls return payment terms and do not execute, and the guarantee that absent schemas are not fabricated. Return shape is left to the output schema, which is acceptable.

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

Conciseness4/5

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

Purpose is front-loaded in the first sentence, followed by constraint, price, endpoint and payment behavior. It is terse and largely waste-free, though the price and endpoint sentences read as billing metadata bolted onto the functional description.

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

Completeness3/5

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

The tool takes 14 optional parameters with deep nesting, and the description does not explain which parts of the payload envelope matter for a schema diff. An agent must infer from the schema that only the `schemas` array (with side left/right) is material and that the other containers are ancillary.

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 description coverage is 100%, so the baseline is 3. The description does clarify two things beyond the schema: the left/right semantic of the side values and that all schema data is caller-supplied rather than fetched. It never mentions the remaining payload containers (csv, text, json, files, cycles, samples, downtime, etc.) that dominate the 14 parameters.

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 first sentence gives a specific verb ("Compare") and resource ("left/right ROS topic message types and fields") with the scope qualifier "caller-supplied." No sibling in the list performs a schema diff, so an agent can route this without opening the schema.

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?

"Caller-supplied left/right" implies both sides must be provided, and "missing schemas are not invented" is a useful input constraint. However, there is no explicit when-to-use vs alternative guidance, no statement of what happens with only one side, and no routing to a sibling for related needs.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources