Skip to main content
Glama

Register a control

register_control

Registers a control for an engagement by capturing its type, frequency, linked risks, assertions, and COSO principles to support internal-control reviews.

Instructions

Register a key control with its type, frequency, linked risks, assertions and COSO 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>",
      "description": "<description>",
      "type": "<type>",
      "frequency": "<frequency>"
    },
    "name": "register_control"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNo
typeYes
ownerNo
riskIdsNo
frequencyYes
assertionsNo
principlesNo
descriptionYes
scopeItemIdNo
engagementIdYes

Output Schema

NameRequiredDescriptionDefault
controlYes

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 for a write operation, yet it discloses nothing beyond the field list. It says nothing about permissions, duplicate handling, what happens when a referenced riskId or scopeItemId does not exist, or whether the record is created as key by default.

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; every listed noun maps to a real field. It is appropriately sized for its content, though the terseness is partly what leaves gaps elsewhere.

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

Completeness2/5

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

For a 10-parameter, 4-required creation tool with no annotations and 0% schema description coverage, one sentence is thin. The existence of an output schema excuses it from explaining return values, but it should still cover required inputs and the engagement/scope linkage.

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, and it partially does: it names the concepts behind key, type, frequency, riskIds, assertions and principles (6 of 10). However owner, description, scopeItemId and engagementId — including the required engagementId — get no mention, and the enums for type/frequency are left entirely to 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?

The description pairs a specific verb ('Register') with a specific resource ('a key control') and enumerates the salient attributes (type, frequency, linked risks, assertions, COSO principles). An agent can tell this creates a control record. It does not, however, explicitly distinguish itself from the nearby register_risk or add_scope_item siblings.

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?

There is no statement of when to use this tool versus alternatives, no prerequisites (e.g. that an engagement must exist first), and no note about ordering relative to register_risk even though linked risks are a parameter. Usage must be inferred entirely from the name.

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