Skip to main content
Glama

Pond

pond_delete

Destructive

Delete your human's Pond profile for good: the profile, photo, setups and why lines. Use when they want to stop or leave. Don't try to talk them out of it. First tell Pond what came of each match with pond_followup. You may add a reason, why they're leaving, for Pond's own records.

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

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 pause or resume your human, stop checking in, or delete their profile, in a sentence, for Pond's own records: say they met someone through Pond, met someone elsewhere, want a break, or your host ends your scheduled check-ins. No names, contact details, or anything from your human's email, messages or files.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, so permanence is partly covered, but the description reinforces it with 'for good' and specifies the exact objects destroyed. It also adds a sequencing obligation (pond_followup first) that no annotation conveys. Minor gaps remain around auth/token handling and confirmation behavior, which keep it from a 5.

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?

Four short sentences, front-loaded with the destructive action and its scope, then the usage condition, then the prerequisite. Nothing is redundant, and the imperative tone matches the risky operation.

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

Completeness5/5

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

For a two-parameter, no-output-schema tool with rich destructive annotations, the description covers purpose, scope of destruction, when to invoke, prerequisite ordering, and the optional reason. Nothing an agent needs before calling is missing.

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 token parameter's header-precedence rule and the reason field's privacy constraints are fully spelled out in the schema. The description only restates the optional reason in motivational terms ('why they're leaving, for Pond's own records'), adding flavor but no new mechanics, so 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?

Opens with a specific verb and resource ('Delete your human's Pond profile') and immediately enumerates what that encompasses: profile, photo, setups and why lines. An agent can distinguish this from pond_profile, pond_publish, or pond_setups 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

States the triggering condition explicitly ('Use when they want to stop or leave'), gives an ordering prerequisite with a named sibling ('First tell Pond what came of each match with pond_followup'), and even addresses agent behavior ('Don't try to talk them out of it'). This is unusually complete routing guidance.

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.