Skip to main content
Glama

Control: add or update

control_save
Idempotent

Add a recurring control (access review, backup restore test, vendor review) to your calendar. Requires the organization API key.

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": {
      "control_id": "<control_id>",
      "title": "<title>",
      "every_days": "<every_days>",
      "owner": "<owner>",
      "actor": "<actor>"
    },
    "name": "control_save"
  }
}

Input Schema

NameRequiredDescriptionDefault
actorYesWho is doing this (person or agent)
ownerYesWho is responsible
titleYes
retiredNo
referenceNoFramework reference, e.g. SOC 2 CC6.2 or ISO 27001 A.8.13
control_idYesYour short ID, e.g. backup-restore-test
every_daysYesHow often it must be done, in days (90 = quarterly)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description adds a genuine operational fact beyond the annotations: an organization API key is required. Annotations already declare non-read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered, but the description never explains the upsert semantics implied by idempotentHint=true and the "add or update" title, nor what happens when control_id already exists.

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?

Two short sentences with the action front-loaded and the prerequisite second; no filler. It is efficient, though the brevity is partly what leaves the update behavior unexplained.

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?

For a seven-parameter, five-required mutation tool with no output schema, the description covers the what and the auth prerequisite but not the outcome, the update path, or how scheduling/reminders are derived from every_days. Adequate as a minimum, with clear gaps.

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 71%, so most parameters are self-documented, and the description adds no parameter-level meaning at all. It does not clarify that control_id acts as the upsert key, nor how every_days interacts with the calendar scheduling implied by the description.

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 concrete verb and resource ("Add a recurring control ... to your calendar") and gives three illustrative control types, so an agent can tell what kind of object this creates. It stops short of distinguishing itself from scheduling/listing siblings such as controls_due, and it omits the "or update" half of the title.

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 explicit when-to-use, when-not-to-use, or named alternative; the reader must infer that this is the write path while controls_due is presumably the read path. The only contextual cue is the parenthetical list of control examples, which describes content rather than routing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources