Skip to main content
Glama

Get a COSO principle

get_principle

Retrieve a single COSO principle by framework number or slug, including paraphrased points of focus, to support internal-control reviews and principle-level analysis.

Instructions

Return a single COSO principle by framework number or slug, including its paraphrased points of focus.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_principle"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo
numberNo

Output Schema

NameRequiredDescriptionDefault
foundYes
principleYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

C2.9/5.0
Behavior2/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 falls short: it never states this is a read-only lookup, what happens if the principle is not found or neither identifier is supplied, or how the two lookup modes relate. It only hints at content ('paraphrased points of focus'), which the output schema already covers.

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; the resource and lookup keys come first. It is appropriately sized, though it spends its one sentence without covering usage or identifier rules.

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, and the tool is relatively simple. However, with zero annotations and zero parameter documentation, the mutual exclusivity/requirement rules for id vs number remain unstated, leaving a real gap for a lookup tool with two optional identifiers.

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 must compensate. It partly does by linking the two locators to 'framework number or slug', implying number and id are alternate identifiers, but it never clarifies that id is the slug, whether they are mutually exclusive, or that at least one is required (both are optional in the schema).

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 principle) and names the locator fields (framework number or slug). It implicitly contrasts with list_principles by saying 'single', but never names that sibling, so differentiation is left to inference.

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?

No when-to-use guidance, no conditions, and no alternatives named. An agent must guess whether to reach for list_principles, get_component, or assess_principle instead of this tool.

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