Skip to main content
Glama

Secure Autonomous Register

Get a control

get_control
Read-onlyIdempotent

One control: its definition, the cases where it failed, was absent or held, and the regulations and standards that require, imply or recommend it.

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": {
      "id": "<id>"
    },
    "name": "get_control"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe control ID, such as C-E3. list_controls gives every ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"Control ID such as C-E3"New value: +"The control ID, such as C-E3. list_controls gives every ID."
  2. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds substantive value beyond that by disclosing what the response contains - the control definition, its pass/fail/absent case outcomes, and the linked regulations and standards - which matters given there is no output schema.

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?

It is a single compact sentence with no filler and front-loads the resource being returned. The trade-off is that it is a noun-phrase fragment rather than a complete statement of action, which slightly reduces immediate clarity.

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?

With no output schema, the description carries the burden of explaining return contents and does so reasonably well for a one-parameter read tool. Minor gaps remain around error behavior for unknown IDs and pagination on large case lists.

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 single id parameter is fully documented, including an example (C-E3) and a pointer to list_controls for valid IDs. The description adds no further meaning about the ID, so the baseline of 3 applies.

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 names the specific resource and enumerates its contents (definition, failed/absent/held cases, requiring or recommended regulations), which lets an agent distinguish it from get_case and list_controls. It lacks an explicit verb like 'retrieve', but 'One control' signals the singular-fetch nature clearly.

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 guidance. An agent must infer that this is for fetching a single control by ID versus list_controls for enumeration, and no prerequisites or exclusions are stated in the description itself.

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