Skip to main content
Glama

Default-watch and pinning service

list_alerts

Operator alert surface: STAGED/UNANNOUNCED/PIN_VIOLATED events for the caller's platforms

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and does not state whether this is read-only, whether it consumes/acknowledges alerts, whether results are paginated or limited, or how the three states differ. Only the event-state enumeration adds any behavioral signal.

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 compact sentence with no filler; the scope and state list are front-loaded. It is terse to the point of under-specification, but no sentence is wasted.

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

Completeness2/5

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

No output schema, no annotations, and the description does not describe the shape of returned alerts, ordering, volume, or what an 'operator' caller is. Given the complete absence of structured support, an agent cannot predict what calling this returns.

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 nothing for the description to disambiguate; baseline 4 applies. The mention of 'the caller's platforms' is useful implicitly, as it explains the scope that replaces what would otherwise be a platform parameter.

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 names the resource ('alerts') and enumerates three specific event states (STAGED/UNANNOUNCED/PIN_VIOLATED), which is concrete. However, it is a noun phrase ('Operator alert surface') with no verb, and 'surface' is idiosyncratic jargon rather than a clear statement that this lists/returns events.

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 statement of when to call this versus siblings such as probe, verify_attestation, or delta_run, nor any prerequisite or exclusion. The agent must infer usage entirely from the name and event-state acronyms.

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