Help by DeltaBreen

remove_integration_address

DestructiveIdempotent

Take a test domain's address away. That domain's test tickets are asked nowhere until it has another; nothing on its server changes. Owner only. Ask the person first.

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": {
      "integration_id": "<integration_id>",
      "address_id": "<address_id>"
    },
    "name": "remove_integration_address"
  }
}

Input Schema

Name	Required	Description	Default
`address_id`	Yes	The address's id (a uuid), from list_integration_addresses.
`integration_id`	Yes	The integration's id (a uuid), from list_integrations.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 27, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Goes well beyond the annotations: it explains the downstream consequence (test tickets are asked nowhere until another address is added), clarifies that nothing on the server changes, and names the owner-only auth requirement. That is exactly the kind of context destructiveHint=true doesn't convey on its own.

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?

Three terse sentences, front-loaded with the action, then consequence, then constraints. No padding, though the phrasing 'are asked nowhere until it has another' is slightly convoluted.

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 two-parameter destructive tool with full schema coverage and rich annotations, the description covers consequence, side effects, and auth. Missing only minor details like whether removal is reversible or how to re-add, which are low-impact here.

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 coverage is 100% and both parameters document their uuid source (list_integration_addresses, list_integrations). The description adds nothing about parameters, so it meets the baseline-3 threshold with the schema carrying the load.

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?

States a specific verb and resource: taking away a test domain's address. This is distinguishable from remove_domain/remove_integration (which the description implicitly scopes out by saying only the address goes). However, it never names the sibling add_integration_address or list_integration_addresses, so differentiation relies on inference.

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?

'Owner only. Ask the person first.' gives a prerequisite (permission) and a confirmation caution, which is clear usage context. It doesn't say to check list_integration_addresses first or explain when this is preferable to updating the integration, so no explicit alternatives.

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

All Help by DeltaBreen 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?