Skip to main content
Glama

List alerts

fleet__list_advisories
Read-onlyIdempotent

Open advisories for the agency, severity-first, filterable by severity, category, site, source and whether they are acknowledged. Each says whether it is known to be actively exploited.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows to return. Defaults to 50; capped at 200 server-side.
sourceNoOnly advisories from this source, for example royally_security_sweep for the security sweep.
site_idNoOnly advisories affecting this site.
categoryNoExact-match filter on advisory category. Omit for all categories.
severityNoExact-match filter on advisory severity. Omit for all severities.
acknowledgedNotrue for acknowledged advisories only, false for ones not yet acknowledged.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / category / enum
      Previous value: -[
      -  "vulnerability",
      -  "update_available",
      -  "security_incident",
      -  "performance",
      -  "compliance",
      -  "backup",
      -  "seo"
      -]New value: +[
      +  "vulnerability",
      +  "update_available",
      +  "security_incident",
      +  "performance",
      +  "compliance",
      +  "backup",
      +  "seo",
      +  "changes"
      +]
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds genuine behavior not in structured data: results are sorted severity-first and each row carries an actively-exploited flag, which matters for triage decisions. The ambiguity of 'Open' (versus the separate acknowledged filter) is a minor gap, not a contradiction.

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?

Two tight sentences with the resource and scope front-loaded and behavior detail second. The enumerated filter list partly duplicates the schema and could be trimmed, but nothing is padded or vague.

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?

For a six-parameter read-only list with no output schema, the description covers scope, ordering, filterability and one return field (actively-exploited). It does not mention the 50-row default or 200 cap behavior, but those are fully specified in the schema, so the gap is small.

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

Parameters3/5

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

Schema description coverage is 100%, so every parameter is already documented, and the description's filter list (severity, category, site, source, acknowledged) largely restates the schema. The only added meaning is the default sort order ('severity-first'), which is not expressible through any parameter. Baseline 3 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?

States a specific verb and resource ('Open advisories for the agency') plus ordering ('severity-first'), which is more than the title 'List alerts' conveys. It does not name sibling tools such as fleet__get_advisory (single advisory) or fleet__security_triage, so an agent must infer the boundary from names alone.

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

Usage Guidelines3/5

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

The word 'Open' scopes the tool to unresolved items and the filter list implies drill-down usage, which is useful implicit guidance. However, there is no explicit statement of when to use this versus fleet__get_advisory for a single record or fleet__security_triage for triage, and no note on what 'open' excludes.

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