Skip to main content
Glama

List exceptions

list_exceptions

Retrieve all exceptions recorded for a specific engagement to review and resolve control-testing issues.

Instructions

List the exceptions recorded for an engagement.

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": {
      "engagementId": "<engagementId>"
    },
    "name": "list_exceptions"
  }
}

Input Schema

NameRequiredDescriptionDefault
engagementIdYes

Output Schema

NameRequiredDescriptionDefault
countYes
exceptionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does not disclose that this is a read-only listing, whether results are paginated or ordered, or what happens if the engagement has no exceptions or does not exist.

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 efficient sentence with no filler, front-loading the verb and resource. It is appropriately short, though it errs on the side of under-specification rather than waste.

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 values need not be explained. Still, for a read tool with no annotations and an undocumented required parameter, the description leaves gaps about scope, ordering, and behavior that a complete definition would cover.

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 description coverage is 0% and the single required parameter engagementId has no description in the schema or the description text. The description only vaguely implies the parameter via 'for an engagement', without stating expected format (the schema pattern) or whether it must reference an existing engagement.

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 (List) and resource (exceptions) scoped to an engagement, so the operation is unambiguous. However, it makes no attempt to distinguish itself from siblings like list_deficiencies or list_test_results, which an agent could easily confuse it with.

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 guidance on when to use this versus alternatives such as note_exception (to create one) or list_deficiencies. The only implied usage is the 'for an engagement' scope, which is thin.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.