Geode

Exchange: browse all listings

geode_exchange_browse_all_listings

Read-only

Browse all public listings on the Geode private coin exchange (offer coin, asking coin, price, payment method, inventory, location). Read-only; no signature. Optional caller: the account whose view to read (for caller-dependent results). Results are paginated with offset and limit (default 50, max 200).

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

Input Schema

Name	Required	Description
`limit`	No	Items to return (default 50, max 200)
`caller`	No	Optional account address (SS58) to run the query as
`offset`	No	Items to skip (default 0)

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 17, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, destructiveHint, openWorldHint), so the bar is lower. The description still adds useful context beyond them: 'no signature' discloses that no authentication is required, and it describes pagination behavior with offset/limit defaults.

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 dense sentences, front-loaded with the resource and scope before parameters and pagination. Every clause carries information; nothing is wasted.

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 paginated read-only list tool with annotations covering safety and a fully documented schema, this is nearly complete: it names returned fields, auth requirements, and pagination. It lacks any note on ordering or default filters, which keeps it short of a 5.

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%, so the baseline is 3; limit and offset are merely restated. However, the description adds real meaning for `caller` ('the account whose view to read (for caller-dependent results)') beyond the schema's terse 'account address to run the query as'.

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 states a specific verb (Browse) and resource (all public listings on the Geode coin exchange), and even enumerates the returned fields (offer coin, asking coin, price, payment method, inventory, location). The word 'public' and 'all' distinguishes it from the sibling geode_exchange_view_my_listings.

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 context is implied by 'all public listings' and 'read-only; no signature', but the description never names alternatives such as geode_exchange_view_my_listings or explains when an agent should choose this over them. No explicit when/when-not guidance is given.

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

All Geode tools Inspect

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

Need Help?