Skip to main content
Glama

Coline

List senders

alert_senders_list
Read-onlyIdempotent

Lists the tools that sent events to addresses you can see: what each is, whether it's verified, how much it sent.

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": {
      "workspace": "<workspace>"
    },
    "name": "alert_senders_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressIdNo
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
sendersYes

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, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds that results are permission-scoped ('addresses you can see') and hints at per-sender fields, but says nothing about pagination, ordering, or whether senders with no traffic appear.

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 a compact colon list of returned attributes and no filler. It is efficient, though the compressed phrasing ('what each is') is slightly vague for machine interpretation.

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?

An output schema exists, so return formatting needn't be restated, and annotations cover safety. However, for a list tool with an optional filter of undocumented meaning, the description leaves the addressId behavior and result scope under-specified.

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 coverage is only 50%: workspace is documented in the schema, but addressId has no description anywhere. The description never mentions the addressId filter, so it fails to compensate for the gap and an agent cannot tell whether passing addressId narrows the result to one address or changes the response shape.

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 ('Lists') and a resource defined in plain language ('the tools that sent events'), which helpfully disambiguates 'sender' as a tool rather than a person or address. It also scopes results to 'addresses you can see', though it never contrasts itself with alert_events_list or alert_addresses_list.

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 explicit when-to-use guidance and no mention of alternatives such as alert_sender_get for detail on a single sender, or alert_events_list for the events themselves. Usage is only inferable from the purpose sentence.

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