Skip to main content
Glama

List suppressions

list_suppressions
Read-only

List addresses on the suppression list (email is not sent to them).

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

Input Schema

NameRequiredDescriptionDefault
pageNo
searchNo
per_pageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful domain semantics (suppressed addresses receive no email) but says nothing about pagination, result size, ordering, or what a result record contains.

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 front-loaded sentence with no filler and no repetition of the title. It is efficient, though the brevity is partly the cause of the missing parameter and usage detail rather than pure economy.

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

Completeness3/5

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

For a simple read-only listing tool with no output schema, the annotations plus description cover the basics of what it does. However, with three undocumented parameters and no hint about result shape or pagination, an agent still lacks what it needs to invoke with the right arguments.

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

Parameters2/5

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

Schema description coverage is 0% for all three parameters, and the description does not mention page, search, or per_page at all. It does not clarify whether search matches the address substring or exact value, nor how per_page interacts with pagination, so it fails to compensate for the schema gap.

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?

"List addresses on the suppression list" gives a specific verb and resource, and the parenthetical explains what a suppression actually means operationally (mail is not delivered to those addresses). It is clear and distinguishable from siblings like list_domains or list_messages, though it never explicitly contrasts itself with them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no guidance on when an agent should call this versus add_suppression or get_stats, nor any stated prerequisites. Only the implicit 'this is the listing endpoint' usage is conveyed by the name and description.

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.

Resources