Skip to main content
Glama

Notification contacts

list_notification_contacts
Read-only

Contacts that receive alerts, whether each is confirmed, and for phone contacts their latest text or call and whether it was delivered.

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_notification_contacts"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context by disclosing that 'confirmed' status is reported per contact and that phone contacts expose their latest text/call with delivery outcome. It says nothing about ordering, pagination, or whether unconfirmed contacts are included.

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 sentence with no redundant wording, and the resource comes before the detail fields. It is a sentence fragment rather than a full clause, and a brief leading verb (e.g. 'List...') would make it sharper, but nothing is wasted.

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?

With no output schema, the description must carry the return content, and it does: contacts, confirmation flags, and the last text/call plus delivery status. For a zero-parameter read tool this is close to sufficient; only the collection shape (list, ordering) and whether it covers all contacts are left implicit.

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

Parameters4/5

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

The tool takes zero parameters, so there is no parameter semantics to document and the baseline of 4 applies. The description spends its space on output content instead, which 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 precisely: contacts that receive alerts, plus the per-contact fields returned (confirmation status, latest text/call and delivery outcome). It lacks an explicit verb but the plural noun phrase plus the tool name make the list-read operation unmistakable. It does not name siblings such as add_notification_contact or confirm_notification_contact to draw a boundary.

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 guidance at all: no statement about when to call this versus add_notification_contact, confirm_notification_contact, or test_notification_contact, and no preconditions. The reader must infer the retrieval-only role from the name alone.

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