Skip to main content
Glama

List COSO principles

list_principles

Retrieve the 17 COSO ICIF-2013 internal control principles, optionally filtered by one of the five components, to scope and structure internal-control reviews.

Instructions

List the 17 principles of the COSO ICIF-2013, optionally filtered to a single component.

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

Input Schema

NameRequiredDescriptionDefault
componentNoRestrict to a single component id.

Output Schema

NameRequiredDescriptionDefault
countYes
frameworkYes
principlesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.8/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. It discloses the fixed size of the result set (17) and that filtering is optional, which establishes this is a bounded read, but says nothing about ordering, permissions, or whether the framework list is static.

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?

A single front-loaded sentence with no waste; the resource, the scope (17 principles), and the optional narrowing are all stated up front.

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?

An output schema exists and parameter coverage is complete, so return format and filter values need no elaboration. For a simple enumeration tool the description is nearly sufficient, missing only ordering/volatility detail.

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 coverage is 100% and the enum values are self-describing, so the schema does the heavy lifting. The description only restates that the filter narrows to a single component, adding no syntax or semantics beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (List) and resource (the 17 COSO ICIF-2013 principles), and quantifies the result set. This clearly separates it from get_principle (single lookup), assess_principle, and list_components among the sibling tools.

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?

"optionally filtered to a single component" implies when the component parameter is worth using, but there is no explicit guidance on when to prefer this over get_principle or list_components, and no stated exclusions or prerequisites.

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