Skip to main content
Glama

Assess a COSO component (indicators)

assess_component

Report coverage indicators for a single COSO component by aggregating its principles, so you can assess internal-control status per component within an engagement.

Instructions

Report coverage indicators for one COSO component, aggregating its principles.

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>",
      "id": "<id>"
    },
    "name": "assess_component"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
engagementIdYes

Output Schema

NameRequiredDescriptionDefault
foundYes
assessmentYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3/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 disclose the aggregation behavior (rolls up principle-level indicators), but says nothing about whether this is a read-only computation, what permissions or engagement state it needs, or whether it mutates stored data. For an annotation-free tool this is a notable gap.

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 no filler, and the scoping constraint ('one COSO component') appears early. It is efficient, though the terseness borders on under-specification rather than genuine conciseness.

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. However, for an assessment/compute tool with no annotations and no parameter documentation, the description is thin: it omits usage routing, permissions, and the meaning of the engagement context, leaving real gaps.

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 adds no parameter meaning at all. The 'id' enum is self-documenting via its five values, but 'engagementId' is left entirely unexplained, and nothing states what 'id' selects relative to the component hierarchy. With 2 params at 0% coverage, the description should compensate but does not.

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 ('Report') and resource ('coverage indicators for one COSO component'). 'Aggregating its principles' implicitly separates it from the sibling assess_principle by signalling it operates one level up the hierarchy, though it never names that sibling explicitly.

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 only implied: the phrase 'for one COSO component' hints at the scoping constraint and 'aggregating its principles' hints at the relationship to assess_principle, but there is no explicit when-to-use, when-not, or alternative routing. No exclusions or prerequisites are stated.

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