Skip to main content
Glama

Classify a deficiency

classify_deficiency

Classifies control deficiencies as deficiency, significant deficiency, or material weakness from likelihood and magnitude, escalating when controls are pervasive.

Instructions

Classify a control deficiency as deficiency / significant deficiency / material weakness from likelihood × magnitude (escalates for a pervasive control).

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>",
      "title": "<title>",
      "description": "<description>",
      "likelihood": "<likelihood>",
      "magnitude": "<magnitude>"
    },
    "name": "classify_deficiency"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes
controlIdNo
magnitudeYes
pervasiveNo
likelihoodYes
descriptionYes
remediationNo
engagementIdYes
exceptionIdsNo
testResultIdNo
compensatingControlNo

Output Schema

NameRequiredDescriptionDefault
deficiencyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.1/5.0
Behavior3/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 it does disclose the core classification logic including the pervasive-control escalation. It says nothing about persistence/side effects (does calling this create or update a deficiency record?), idempotency, required permissions, or whether re-classification is allowed, which are material for what appears to be a mutating tool.

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 dense sentence with no filler, and the classifier logic and outcome set are front-loaded where an agent needs them. The parenthetical '(escalates for a pervasive control)' is terse to the point of being slightly cryptic, which keeps it from a 5.

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?

Output schema presence excuses it from explaining return values, but for an 11-parameter tool with a nested remediation object linkages (exceptionIds, testResultId, compensatingControl) the description leaves too much unexplained: no hint that remediation details are attached here, no guidance on which identifiers are required versus optional, and no behavioral scope for the resulting record.

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% across 11 parameters, and the description only names three of them (likelihood, magnitude, pervasive). The required engagementId, title, description, plus controlId, testResultId, exceptionIds, compensatingControl, and the nested remediation object are undocumented in both schema and prose, leaving most parameters ambiguous.

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 (classify) and resource (control deficiency) plus the exact output categories (deficiency / significant deficiency / material weakness), which is far more precise than a tautology. It does not, however, name or distinguish itself from near siblings such as aggregate_deficiencies or list_deficiencies, so a 4 rather than 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 Guidelines3/5

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

Usage is implicit: the decision rule (likelihood × magnitude, escalation for pervasive) tells the agent the inputs it needs, but there is no explicit when-to-use versus when-not, no statement of prerequisites (an existing engagement/test result), and no routing to aggregate_deficiencies or record_test_result.

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