Skip to main content
Glama
Sign In

BotInfo — Advanced Robot Market Data

by ai.botinfo
OverviewDiscussionsAdmin

Get today's listed prices for a robot model

robot_price_today
Read-onlyIdempotent

Get today's listed price of every listing BotInfo's daily price watch read for a robot model, across the maker's own store and dealers: the listing name, price in USD, stock flag and read date. Dealers are labelled by letter, not named; the maker's store is named. A listed price is not a quote: taxes, shipping and options can change the total. Today's read only, no price history. Use it to see the spread of prices for one model on one day.

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

Input Schema

NameRequiredDescriptionDefault
robotYesRobot model, e.g. 'Unitree G1' or 'unitree r1'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/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 safety profile is covered. The description adds genuinely useful behavior beyond that: the source scope (maker's store plus dealers), dealer anonymization by letter, the returned fields, and the caveat that taxes/shipping/options can change the total. It stops short of stating freshness timing or rate limits, which keeps it at 4 rather than 5.

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?

The scope and return fields are front-loaded, and the caveat and time-window limit follow in short order. The opening sentence is long and comma-heavy, but every sentence still carries distinct information.

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?

With no output schema, the description usefully enumerates what comes back (listing name, USD price, stock flag, read date) and explains the dealer-letter labelling quirk. It is nearly complete for a single-parameter read tool, missing only how model-name matching and result ordering work.

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 coverage is 100% and the single 'robot' parameter already carries a description with examples. The description reinforces that it takes one model and that results are for that model only, but adds no matching rules (exact vs fuzzy name matching) beyond what the schema shows, so the baseline 3 applies.

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 names a specific verb and resource — 'Get today's listed price of every listing ... for a robot model' — and immediately distinguishes this data from a quote, which separates it from request_quote and get_buy_route among the siblings.

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?

It states the use case ('see the spread of prices for one model on one day') and an explicit exclusion ('Today's read only, no price history'). It does not name request_quote as the alternative when the agent actually wants a firm price, though the 'listed price is not a quote' remark strongly implies that routing.

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

All BotInfo — Advanced Robot Market Data 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