Geode

Market: rate a buyer

geode_market_rate_a_buyer

Seller: rate (1 to 5) and review the buyer of one of your orders. Writes to the chain: this prepares an unsigned transaction (an intent) for signer; nothing happens until you sign it with geode-local-signer and submit it with geode_submit_intent.

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": {
      "signer": "<signer>",
      "buyer": "<buyer>",
      "rating": "<rating>",
      "review": "<review>",
      "order_id": "<order_id>"
    },
    "name": "geode_market_rate_a_buyer"
  }
}

Input Schema

Name	Required	Description
`buyer`	Yes	Geode account address (SS58)
`rating`	Yes	Non-negative integer as a string of digits
`review`	Yes	UTF-8 text, at most 2048 bytes; no control or invisible characters
`signer`	Yes	Your account address (SS58). The transaction is prepared for this account; you sign it on your own machine with geode-local-signer.
`order_id`	Yes	0x-prefixed 32-byte hex id

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 17, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the annotations by disclosing the two-step intent model: the call only prepares an unsigned transaction for `signer`, and nothing is committed until geode-local-signer signs and geode_submit_intent submits. This is exactly the behavioral context an agent needs to avoid assuming an immediate on-chain write.

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 tight sentences. The rate/review action is front-loaded, and the chain-write caveat follows immediately. Every clause carries information; nothing is redundant.

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 mutation tool with no output schema, it adequately explains the intent/sign/submit lifecycle. It leaves out whether a rating is final or editable and any fee/gas implications, which would be useful for a one-shot chain write.

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 baseline is 3, but the description adds the rating bound of "1 to 5" that the schema's "non-negative integer as a string" does not state, and it reinforces that `signer` is the account the transaction is prepared for. Review length limits and order_id format remain schema-only.

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 (rate/review) and resource (the buyer of one of your orders), with the seller-side scope made explicit in the first word. This cleanly separates it from the sibling geode_market_rate_a_product_or_service without the agent needing to open either schema.

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?

"Seller: ... the buyer of one of your orders" implies the precondition (you are the seller with a completed order) and gives clear context for when it applies. It does not explicitly name the alternative (rating a product/service) or state exclusions, so it falls short of a 5.

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?