Skip to main content
Glama

Toll — coin, agent and pre-sign checks on Robinhood Chain

Stop watching a coin

unwatch_coin
DestructiveIdempotent

Remove one of your coin watches on Robinhood Chain by its watch id. Needs a Toll key.

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": {
      "id": "<id>"
    },
    "name": "unwatch_coin"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe watch id (a uuid)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"The watch id (a uuid) from my_watches"New value: +"The watch id (a uuid)"
  2. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description adds a genuinely operational fact not in any structured field: the call "Needs a Toll key", which tells the agent an auth credential must be obtained first. It omits error behavior for a nonexistent id, but against rich annotations this is a solid contribution.

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 short sentences with no filler; the action and scope come first and the auth requirement follows. Every clause carries information an agent needs.

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?

For a one-parameter, no-output-schema mutation with full annotation coverage, the definition covers action, target, identifier and auth prerequisite. Only the outcome of an invalid or already-removed id is left unstated, which is a minor gap at this complexity level.

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?

There is a single required parameter with 100% schema description coverage, and the schema already says it is a uuid watch id with a 40-character cap. The description only restates "by its watch id", adding no format or sourcing detail beyond the schema, so the baseline 3 applies.

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 names a specific verb and resource ("Remove one of your coin watches") and scopes it to "Robinhood Chain" and lookup "by its watch id", which separates it from watch_coin and from the wallet-oriented sibling unwatch_wallet. It stops short of explicitly naming the counterpart tools, so it is clear but not fully differentiated in-text.

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 "Remove one of your coin watches" — an agent can infer this is the teardown counterpart to watch_coin. There is no explicit when-to-use/when-not-to-use statement, no mention of unwatch_wallet as the alternative for wallet watches, and no note on what to do if the watch id is unknown.

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.