Skip to main content
Glama

Framework integration check

framework_integration_check

Verify that all five COSO components have recorded coverage and that required principles are addressed for a given engagement.

Instructions

Check that all five COSO components have some recorded coverage and that principles are addressed.

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

Input Schema

NameRequiredDescriptionDefault
engagementIdYes

Output Schema

NameRequiredDescriptionDefault
componentsYes
integrationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.2/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. It does disclose the substantive logic of the check (coverage across all five components, principles addressed), which tells the agent what a pass/fail means. It does not state that the operation is read-only/non-mutating, nor whether it errors or returns findings — gaps that matter given zero annotation coverage.

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 efficient sentence with no filler, and the core check condition is front-loaded. Appropriately sized for the tool's scope.

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, which lightens the burden. Still, the description omits any when-to-use guidance, does not explain the engagementId parameter, and says nothing about failure behavior — leaving meaningful gaps for a validation tool with no annotations.

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 never mentions engagementId or scopes the check to a given engagement. With a single parameter that is fairly self-explanatory by name, the omission is not fatal, but the description does nothing to compensate for the missing schema documentation.

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 (check) and a specific subject (whether all five COSO components have recorded coverage and principles are addressed). This distinguishes it from the sibling assessment tools like assess_component and assess_principle, which evaluate a single component or principle rather than framework-wide integration. It stops short of naming those siblings 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?

The check condition (all five components covered, principles addressed) implies when the tool is relevant — as an aggregate readiness/coverage validation. However, it never states when to call it versus assess_component, assess_principle, or get_component, nor any prerequisites or timing in the workflow. Usage is inferred rather than stated.

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