Skip to main content
Glama

Loyal Spark Holder

Create P2P Offer

create_p2p_offer

Create a P2P swap intent: offer loyalty tokens in exchange for another B20/ERC-20 token amount.

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": {
      "offer_token_address": "<offer_token_address>",
      "offer_amount": "<offer_amount>",
      "request_token_address": "<request_token_address>",
      "request_amount": "<request_amount>"
    },
    "name": "create_p2p_offer"
  }
}

Input Schema

NameRequiredDescriptionDefault
offer_amountYesAmount of offer token (whole units).
request_amountYesAmount of request token (whole units).
offer_token_addressYesToken you are offering.
request_token_addressYesToken you want in return.

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 this is a non-readonly, non-destructive, non-idempotent mutation. The description adds real value by calling the result an 'intent', signaling that no swap executes immediately and a counterparty must accept. It stops short of saying whether tokens are escrowed, whether an approval is required, or what happens on repeated calls.

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 tight sentence with the verb and resource front-loaded and the economic semantics appended. No filler, no restatement of the title, nothing to trim.

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?

With annotations covering the safety profile and a fully documented schema, the description covers the essentials for a mutation tool. It is still thin on lifecycle context — what the created offer's initial state is and how it relates to accept/cancel — which would help an agent sequence calls correctly.

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 description coverage is 100%, so all four parameters are already documented with patterns and unit notes, making 3 the baseline. The description contributes a small extra nuance by implying the offer side is loyalty tokens while the request side may be B20/ERC-20, but adds nothing about units, limits, or address validation 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: 'Create a P2P swap intent.' The added clause 'offer loyalty tokens in exchange for another B20/ERC-20 token amount' pins down the two-sided nature of the object being created. It does not explicitly contrast with accept_p2p_offer or cancel_p2p_offer, but the create verb makes the distinction reasonably evident.

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 is implied by 'Create a P2P swap intent' — an agent can infer this is the entry point for proposing a swap before acceptance. However, there is no explicit when-to-use guidance, no preconditions (e.g., holding the offer token, allowances), and no reference to the sibling tools that handle the rest of the offer lifecycle.

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