Skip to main content
Glama

Coline

Get a sender

alert_sender_get
Read-onlyIdempotent

A sender's page: what it is, whether it's verified, what it sent, what was shown and what stayed quiet and why, the rules that apply.

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

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
senderYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

C2.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive behavior, so the safety profile is covered. The description adds real value beyond that by enumerating the domain of content returned: verification state, send history, what was displayed versus suppressed and the reason, and applicable rules. It omits access requirements and error/not-found behavior, which keeps it out of the top band.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single compact sentence with no filler, but it is not front-loaded: it opens with a vague noun ('A sender's page') instead of the operation, and the clause list ('what stayed quiet and why') is evocative rather than precise. The size is fine; the ordering and phrasing are the issue.

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 shape need not be explained, and annotations carry the safety profile. For a two-parameter read tool the description is adequate, but it leaves out how to obtain senderId and when this tool beats the list sibling, which is the remaining gap an agent would hit at call time.

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 50%: the workspace parameter is documented in-schema as a slug from workspaces.list, but senderId carries only string length constraints. The description implies the identity of a 'sender' but adds no format, provenance, or lookup guidance for the undocumented parameter, so it does not compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a noun-phrase inventory of a sender's record ('what it is, whether it's verified, what it sent...') rather than a verb+resource statement. It never says explicitly that it retrieves a single sender by ID, and it never distinguishes itself from alert_senders_list or alert_address_get, so the agent must infer the read-one shape from the name and annotations.

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 when-to-use or when-not-to-use guidance, and no named alternative. An agent cannot tell from the description alone whether to call this or alert_senders_list, nor what prerequisites (e.g., obtaining a senderId) exist.

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