Skip to main content
Glama
Sign In

Saypage

by ai.saypage
OverviewDiscussionsAdmin

Delete collected email

delete_email
Destructive

Forget an address list_emails returns, everywhere: when its owner asks.

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": {
      "email": "<email>"
    },
    "name": "delete_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesThe address

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare destructiveHint=true and non-read-only, so irreversibility is pre-covered. The description adds genuinely new scope information: the deletion happens "everywhere," i.e. it is global across all locations the address appears, not just the list entry. That is a meaningful behavioral trait beyond the annotation set.

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 short sentence with the resource and the global scope front-loaded. Nothing is wasted, though the trailing clause "when its owner asks" is telegraphic and takes a moment to parse.

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?

One parameter, an output schema to describe returns, and annotations covering the destructive profile — the remaining burden is scope, which "everywhere" addresses. The tool is adequately specified for an agent to invoke it correctly; only the exact blast radius of "everywhere" stays loose.

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

Parameters4/5

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

Schema coverage is 100% and the schema only says "The address," but the description constrains the value to an address that list_emails returns — a provenance requirement the schema does not express. That extra constraint is real value over structured data.

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?

"Forget an address list_emails returns, everywhere" identifies both the verb (removal) and the resource (an address previously collected via list_emails), and it names the sibling that produces the input. The metaphorical verb "forget" instead of "delete" slightly softens precision, but the tool's intent 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?

"when its owner asks" does supply a real trigger condition — a data-subject erasure request — which is more than most delete tools offer. However, it gives no exclusions, no prerequisites (e.g. does it require the address to exist first?), and no alternative tools for related cleanup.

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

All Saypage toolsInspect
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