Help by DeltaBreen

list_integration_addresses

Read-only

An integration's addresses for its site's test domains, and the test domains, so each can be given one. A test ticket from a test domain is asked at that domain's own address, and nowhere while it has none; live tickets are asked at the integration's URL. Secrets are never included.

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>"
    },
    "name": "list_integration_addresses"
  }
}

Input Schema

Name	Required	Description	Default
`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

A3.7/5.0

Behavior4/5

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

Annotations already mark this as read-only and non-open-world, and the description adds meaningful context: test tickets are routed at their test domain's own address, nowhere when no address exists, live tickets use the integration URL, and secrets are never included. It does not discuss pagination or auth, but it adds substantial behavioral detail beyond the annotations.

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?

The description is short and avoids filler. The first sentence is grammatically awkward and does not front-load a clear verb, but the overall size is appropriate for a simple list tool.

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 simple read-only list tool with complete schema coverage and no output schema, the description gives enough context about what is returned: addresses and test domains, with secrets excluded. It could be slightly clearer about whether all test domains or only unaddressed ones are returned.

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 single integration_id parameter is documented in the schema with a reference to list_integrations. The description adds no further parameter meaning, so the baseline of 3 is appropriate.

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?

The description identifies the resource clearly: an integration's addresses for its site's test domains, plus the test domains themselves. It does not explicitly use a verb like 'list' and does not differentiate from siblings such as add_integration_address or remove_integration_address, but the purpose is still understandable.

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?

Usage is only implied through 'so each can be given one,' suggesting this is used to find test domains that need an address. There is no explicit when-to-use guidance, no exclusions, and no named 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?