Skip to main content
Glama

TokenBank — tokenized real-world assets

Compare instruments

compare_assets
Read-onlyIdempotent

Puts two to six instruments side by side on the fields that distinguish them: yield, risk, minimum, custody, the three KYC gates, target/area, issuer and verification date.

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": {
      "tickers": "<tickers>"
    },
    "name": "compare_assets"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickersYese.g. ["USDY", "OUSG", "BUIDL"]

Output Schema

NameRequiredDescriptionDefault
comparedYes
notFoundNo
readThisNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered externally. The description adds only the informational note that the comparison covers specific distinguishing fields, which helps the agent judge whether the answer will address its question, but it says nothing about how missing/unverified data is handled or what happens if a ticker is unknown.

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?

One tightly packed sentence with the scope constraint front-loaded and no filler. The trailing list of compared fields is dense but earns its place by telling the agent what evidence it will get back. The phrase 'the three KYC gates' is slightly compressed but still readable.

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 an output schema present, rich read-only annotations, and a single fully documented parameter, the description only needs to convey scope and comparison coverage, which it does. The remaining gap is routing guidance against sibling comparison tools, which is a moderate omission rather than a functional one.

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?

Only one parameter exists and its schema description already supplies a concrete example array, so the schema carries the parameter burden. The description's 'two to six instruments' mirrors the minItems/maxItems already declared in the schema, adding emphasis but no new semantic detail. Baseline 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 gives a specific verb ('puts side by side') plus the resource ('instruments') and a concrete scope of two to six, then enumerates the dimensions compared (yield, risk, minimum, custody, KYC gates, target/area, issuer, verification date). An agent can immediately tell this is a multi-item comparison tool rather than a single-lookup tool. It stops short of naming how it differs from the other compare_* siblings, which keeps it off a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It implies usage (you invoke it when you need to weigh instruments against each other) but never states when to use it versus alternatives such as compare_tokenized_access or compare_with_savings_account, nor any exclusions or prerequisites. The 2-6 range is a hard constraint, not guidance about when this tool is the right call.

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