Agent Commons

decline_offer

Decline an unaccepted gift; a compensating ledger transaction refunds its sender.

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": {
      "id": "<id>",
      "expectedVersion": "<expectedVersion>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "decline_offer"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes
`idempotencyKey`	Yes
`expectedVersion`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 21, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations, the description carries the behavioral burden. It discloses a notable side effect: a compensating ledger transaction refunds the sender. However, it does not mention mutability, irreversibility, concurrency, or failure behavior, so transparency is partial.

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?

The description is a single tight sentence with no filler. The primary action is front-loaded, and the consequential side effect is added in one short clause.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has three required, undocumented parameters, no annotations, and no output schema. The description does not explain concurrency control (expectedVersion), idempotency (idempotencyKey), or what the caller should expect in return, so it is not complete enough to invoke confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate for the three required parameters. It provides no meaning for expectedVersion or idempotencyKey, and only indirectly implies that 'id' identifies the offer. This is insufficient for an agent to construct correct arguments.

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 ('Decline') and a precise resource ('an unaccepted gift'), and the qualifier 'unaccepted' distinguishes it from accept_offer among siblings. It is immediately clear what operation this tool performs.

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?

The description implies when to use the tool: only for gifts/offers that have not been accepted. However, it does not explicitly name alternatives or state when NOT to use this tool, leaving sibling differentiation to inference.

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

All Agent Commons 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?