GoodSender

Edit Sender Identity

edit_sender_identity

DestructiveIdempotent

Update display name for an existing sender identity. Does not change email or domain.

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": {
      "Sender": "<Sender>"
    },
    "name": "edit_sender_identity"
  }
}

Input Schema

Name	Required	Description	Default
`Sender`	Yes	Sender email and new display name (name may be empty to clear).

Output Schema

Name	Required	Description	Default
`Result`	Yes	Result of the operation.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 2, 2026
- addedInput schema / properties / Sender / properties / Address / description
```
Added value: +"Email address, e.g. ada@example.com."
```
- addedInput schema / properties / Sender / properties / Name / description
```
Added value: +"Optional display name shown with the address, e.g. Ada Lovelace."
```
First observedNov 2, 2026

TDQS

A4.8/5.0

Behavior4/5

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

While the annotations mark the operation as destructive and a mutation, the description reinforces the behavioral context by specifying that it is an 'Update' operation on an 'existing' identity. This clearly signals it modifies state rather than creating new state.

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 definition is brief and extremely focused. The first sentence captures the entire purpose, and the second provides necessary boundaries, achieving perfect efficiency.

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?

Given that it is an update tool, it is highly effective. It clarifies the scope of the edit (only the display name) and confirms the identity must exist, leaving no ambiguity about its function within the library.

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

Parameters5/5

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

The description adds functional constraints that go beyond the schema, explicitly forbidding changes to email or domain. This context helps the agent understand the tool's limits, even though the schema coverage is complete.

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 uses clear action verbs ('Update') and specifies the target resource ('sender identity') and the exact attribute being modified ('display name'). This is precise and allows easy differentiation from related tools like create_sender_identity.

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?

It provides strong usage constraints by explicitly stating what the tool *does* change and what it *does not* change ('Does not change email or domain'), which is crucial for preventing misuse by the agent.

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

All GoodSender 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.