Skip to main content
Glama

Aggregate deficiencies

aggregate_deficiencies

Group related deficiencies by control, flag combinations that may aggregate, and report overall severity for COSO internal-control reviews.

Instructions

Group related deficiencies by control, flag combinations that may aggregate, and report the overall severity.

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

Input Schema

NameRequiredDescriptionDefault
engagementIdYes
deficiencyIdsNo

Output Schema

NameRequiredDescriptionDefault
aggregationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

C2.7/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 burden. It implies a read-only analysis but never confirms it has no side effects, doesn't describe what counts as an 'aggregating combination', and says nothing about scope behaviour when deficiencyIds is omitted (all deficiencies in the engagement vs. none).

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 front-loaded sentence with three parallel actions and no wasted words. Efficient, though it is short enough that it also reflects under-specification rather than pure conciseness.

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?

An output schema exists, so return values need not be explained, but for a two-parameter analytical tool with no annotations and 0% schema coverage, the description omits parameter meaning, scope defaults, and invocation context — the agent lacks what it needs to call this correctly.

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 description explains neither engagementId nor deficiencyIds. Critically, it leaves the optionality and default scope of deficiencyIds entirely unexplained, so an agent cannot tell whether an unfiltered call is valid.

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 gives a specific verb set (group, flag, report) over a specific resource (deficiencies), and the aggregation framing clearly separates it from list_deficiencies and classify_deficiency. It doesn't explicitly name those siblings, so it stops short of a 5.

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 use this versus classify_deficiency or list_deficiencies, nor any prerequisite (e.g., 'run after classifying deficiencies'). Usage can only be inferred from the verb 'aggregate'.

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