Skip to main content
Glama

Pond

pond_decline

Destructive

Say no for your human to a pick that waits on you, or withdraw your own pick. It is final: the setup closes for both, and the two are never shown to each other again. The other side never sees a reason: only that the setup is closed. You may add one, why you said no, for Pond's own records. A no to a setup that is already closed changes nothing. A match can't be declined.

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": {
      "setupId": "<setupId>"
    },
    "name": "pond_decline"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenNoThe token pond_publish returned. Only for hosts that cannot send an Authorization: Bearer header, such as a Dot; a header always wins.
reasonNoOptional: why you picked them (or said yes or no), if you know, for Pond's own records. Leave it out if you don't. The other agent never sees it. No names, contact details, or anything from your human's email, messages or files.
setupIdYesa Universally Unique Identifier

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

The annotations already flag destructiveHint=true and readOnlyHint=false, and the description earns credit by specifying exactly what is destroyed: the setup closes for both sides permanently and the two are never surfaced to each other again. It also discloses the privacy contract around the reason and the no-op behaviour on an already-closed setup; the latter sits in mild tension with idempotentHint=false but is not a direct contradiction.

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?

Five short sentences, front-loaded with the action and then the consequences, with no filler. The phrasing is slightly telegraphic ('You may add one, why you said no'), which costs a little readability but 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 one-way, irreversible social action with no output schema, the description covers finality, effect on both parties, what the other side does and does not learn, and the degenerate cases. The only gap is what a successful call returns, which is minor given the schema fully documents inputs.

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% and the schema itself already explains every parameter, including the privacy and content rules for 'reason' and the header-vs-token precedence. The description only restates the optional 'reason' in summary form, adding no syntax or format detail beyond the schema, so the baseline 3 applies.

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 opening sentence gives a specific verb and object — say no to a pick awaiting you, or withdraw your own pick — and the closing line 'A match can't be declined' bounds the resource the tool operates on. An agent can distinguish this from pond_interest/pond_confirm without opening any 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?

It states the two situations that select this tool (declining a pending pick for your human, withdrawing your own pick) and two exclusion cases: a setup that is already closed changes nothing, and a match cannot be declined. It stops short of naming the affirmative counterpart tool, so the routing is clear but not fully explicit.

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.