Skip to main content
Glama

Find a currency ID

find_currency
Read-only

Look up Request Network currency IDs by symbol and network so you can set a valid paymentCurrency for crypto invoices.

Instructions

Look up Request Network currency IDs to use as paymentCurrency, e.g. symbol "USDC" on network "base" or "sepolia".

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

Input Schema

NameRequiredDescriptionDefault
symbolNo
networkNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and external-lookup behavior are covered structurally. The description adds some context by identifying the data source as Request Network and the output as payment-currency IDs, but says nothing about whether multiple matches are returned, whether matching is exact or fuzzy, or what happens on an unknown symbol.

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?

A single front-loaded sentence: verb, resource, destination field, then concrete examples. Nothing is redundant and the example values are the highest-value addition given the otherwise undocumented parameters.

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?

For a two-parameter lookup with no output schema, the description should state the return shape (a single currency ID vs. a list of candidate IDs) and the ambiguity of optional inputs. It conveys what the tool is for but leaves the agent guessing about result cardinality and how to handle empty results.

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 0% and neither parameter carries a description, so the description must compensate and only partly does: it supplies example values ('USDC' for symbol, 'base' or 'sepolia' for network) that convey expected casing and network naming. It never explains that both parameters are optional, what happens when only one or neither is supplied, or the meaning of the maxLength limits.

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 ('look up') and resource ('Request Network currency IDs') and states the downstream use ('to use as paymentCurrency'), so an agent can tell this is a lookup helper for invoice/payment-link creation rather than a record operation. It does not explicitly contrast with any sibling, but the resource is self-evidently distinct from the invoice tools.

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?

The phrase 'to use as paymentCurrency' gives clear workflow context: call this before create_invoice or create_payment_link when a currency identifier is needed. There is no explicit exclusion or statement of what to do when no match exists, so it stops short of full when/when-not guidance.

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