Skip to main content
Glama

Get a COSO component

get_component

Retrieves a single COSO component and its associated principles by ID, enabling targeted internal-control review scoping and analysis.

Instructions

Return a single COSO component by id, with 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": {
      "id": "<id>"
    },
    "name": "get_component"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Output Schema

NameRequiredDescriptionDefault
foundYes
componentYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.6/5.0
Behavior3/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. 'Return' implies a read-only, non-mutating operation, and 'with its principles' helpfully discloses that the response expands nested principles rather than the bare component. It does not say what happens on an unrecognized id or whether the result is paginated, leaving behavioral gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One front-loaded sentence with zero filler; the resource, the keying mechanism, and the nested-content disclosure all appear in a single clause. Nothing is padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With a single enum-typed parameter and an output schema present, the definition need not explain return format. It covers the essentials for a simple read, though it omits error behavior for invalid ids and any explicit tie to its list_components/get_principle siblings.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description's only parameter help is 'by id'. The single parameter's enum values (control-environment, risk-assessment, etc.) are self-descriptive, so no syntax explanation is strictly needed, but the description adds no meaning beyond the schema's own 'id'.

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 ('Return') and resource ('a single COSO component') and bounds the scope ('by id', 'single'), which contrasts with the list_components sibling. It stops short of explicitly naming that alternative, but the singular-vs-list distinction is clear from the wording.

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: 'by id' and 'a single component' suggest lookup-by-known-id rather than enumeration, in contrast to list_components. There is no explicit when-to-use, when-not-to-use, or named alternative, so an agent must infer the routing.

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