list_governance_alertsList the organization's governance alerts — quality drops, breaking-change spikes, stale drafts, blocked publishes. Unresolved only by default; capped at the 100 most recent. Requires organization context.
| Name | Required | Description | Default |
|---|---|---|---|
| unresolvedOnly | No | Only alerts nobody has resolved yet (default true) |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description reveals behavior beyond the readOnly annotation: it lists alerts, defaults to unresolved-only, caps at 100, and requires organization context. It does not mention possible side effects or detailed return shape, but for a read-only list operation the core behavior is transparent enough.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One dense, well-structured sentence conveys the resource, examples, defaults, cap, and context requirement without wasted words. It is front-loaded with the core purpose and immediately useful details.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple list operation with one optional boolean parameter, the description covers what it returns, default behavior, result cap, and required context. No output schema exists, and the description provides enough information for an agent to invoke it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The only parameter, unresolvedOnly, is fully described in the schema with its default value and meaning. The description reinforces the default behavior ('Unresolved only by default'), so the agent has complete understanding of the parameter's effect.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb ('List') and resource ('the organization's governance alerts'), and provides concrete examples of alert types (quality drops, breaking-change spikes, stale drafts, blocked publishes). This clearly distinguishes it from related tools like list_alert_policies or resolve_governance_alert.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides important usage context: unresolved-only default, 100-item cap, and required organization context. However, it does not explicitly state when to prefer this tool over sibling tools such as list_alert_policies or get_governance_score, leaving some ambiguity for an agent choosing among similar governance-related tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
The tools are mostly distinct with clear descriptions. Some pairs like get_header_policies vs get_resolved_headers or get_environment_verification vs get_monitoring_sync_status could be slightly confusing, but the descriptions clarify scope and purpose.
All tools follow a consistent snake_case verb_noun pattern (get_, list_, create_, update_, manage_, etc.). Even the few bare verbs like 'search' and 'set_context' are consistent with the naming scheme.
With 165 tools, the server is extremely heavy. This far exceeds the 'too many' threshold of 25+, making it difficult for an agent to navigate and select the right tool efficiently.
The tool surface covers a very broad API lifecycle domain: specs, environments, test cases, monitors, mock servers, security, governance, documentation, and team management. Read and write operations are present across most areas, with no obvious missing core functionality.