Skip to main content
Glama

Loyal Spark Holder

List P2P Offers

list_p2p_offers
Read-onlyIdempotent

List open peer-to-peer token swap offers; optional filter by loyalty token (same price band as merchant GET /offers).

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

Input Schema

NameRequiredDescriptionDefault
token_addressNoOptional filter: offers involving this token.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds that only 'open' offers are returned and references parity with the merchant /offers price band, but says nothing about result size, ordering, or pagination.

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?

A single front-loaded sentence with no wasted wording; the scope ('open') comes before the optional filter clause. The cross-reference to merchant /offers is slightly cryptic but brief.

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 simple read-only list tool with one optional parameter, complete annotations and no output schema, the description covers what it returns (open offers) and how filtering works. Only pagination and result ordering are unaddressed, which is a minor gap.

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 100%, so the token_address parameter is already documented. The description adds a small amount of meaning by framing the filter as 'involving this token' and tying it to the loyalty-token price band, but no format or matching semantics beyond the schema.

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?

States a specific verb and resource ('List open peer-to-peer token swap offers') and scopes it to open offers, which distinguishes it from create/accept/cancel siblings. It does not explicitly name an alternative, but the purpose is unambiguous.

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?

Implies usage through 'optional filter' and a cross-reference to the merchant GET /offers price band, giving some context. There is no explicit when-to-use or when-not-to-use guidance relative to the sibling P2P tools.

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