Skip to main content
Glama

Inspect a bot

bots_inspect
Read-onlyIdempotent

Returns one bot's verified manifest: ok, official, class, free_per_day, price_tfuel, current_ref and its cards (sha256_ok each). Give name OR ref, not both (name wins). Use after bots_discover, before bots_call. Read-only, free, no key. Unknown bot: error not_found.

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": "bots_inspect"
  }
}

Input Schema

NameRequiredDescriptionDefault
refNoOr its listing ref from bots_discover, v3:N, e.g. v3:142
nameNoThe bot's .theta name, e.g. clerk.bots.theta

Output Schema

NameRequiredDescriptionDefault
okNo
blockNo
cardsNo
staleNo
sourceNo
officialNo
current_refNo
price_tfuelNo
free_per_dayNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / name / description
      Previous value: -"e.g. clerk.bots.theta"New value: +"The bot's .theta name, e.g. clerk.bots.theta"
    • changedInput schema / properties / ref / description
      Previous value: -"Listing ref, e.g. v3:142"New value: +"Or its listing ref from bots_discover, v3:N, e.g. v3:142"
    • addedInput schema / properties / ref / pattern
      Added value: +"^v3:\\d{1,9}$"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "block": {
      +      "type": [
      +        "integer",
      +        "null"
      +      ]
      +    },
      +    "cards": {
      +      "items": {
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "current_ref": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "free_per_day": {
      +      "type": "number"
      +    },
      +    "official": {
      +      "type": "boolean"
      +    },
      +    "ok": {
      +      "type": "boolean"
      +    },
      +    "price_tfuel": {
      +      "type": "number"
      +    },
      +    "source": {
      +      "type": "string"
      +    },
      +    "stale": {
      +      "type": "boolean"
      +    }
      +  },
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already cover read-only and idempotency, but the description adds what they don't: the call is free, requires no key, and returns a not_found error for unknown bots. That error contract is the kind of behavioral detail an agent needs before calling.

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?

Three tight sentences, front-loaded with what is returned, followed by selection rule and lifecycle placement. Nothing is padded or repeated.

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?

Though an output schema exists, the inline field list previews the manifest shape and the description covers selection rules, sequencing, cost/auth, and failure mode. There is nothing an agent needs to call this correctly that is missing.

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% and already carries the v3:N pattern and examples, so the schema does most of the work. The description still adds real meaning by declaring the exclusivity and precedence rule ('name wins'), which the schema does not express.

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?

States a specific verb and resource ('Returns one bot's verified manifest') and enumerates the returned fields (ok, official, class, free_per_day, price_tfuel, current_ref, cards). It is clearly distinguishable from the listing sibling bots_discover and the execution sibling bots_call.

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?

Gives explicit ordering guidance ('Use after bots_discover, before bots_call'), which tells the agent both the prerequisite and the next step. The mutual-exclusion rule 'Give name OR ref, not both (name wins)' resolves the only ambiguous choice a caller faces.

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