Skip to main content
Glama

Get a control

get_control
Read-onlyIdempotent

Get one reference control of the open control profiles by its stable id (e.g. "AIGE-CTL-EVAL-002", any case, or "EVAL-002"), its page or JSON URL, or its title: objective, failure modes, scope, enforcement points, verification steps, the evidence it leaves (with schema ids), the failure response, stack layers, patterns, the illustrative mappings (obligation ids, ISO/IEC 42001 Annex A, NIST AI RMF, OWASP, MITRE ATLAS, others), numbered references, implementation notes, open questions, the observation it records and example observations. A draft control specification, open for technical review.

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
idYesControl id, URL or title.

Output Schema

NameRequiredDescriptionDefault
idYes
urlYesThe control on its profile page.
jsonYesThe control record on its own, in the API.
depthYesspecified: written in full; derived: restates a chapter 23 seed; stub: outline with open questions.
layerYes
scopeYes
seedsYes
titleYes
noticeYesIllustrative, not legal advice and not a claim of conformity.
sourceYesCanonical URL of the page this answer comes from; cite it.
statusYesPublication status (draft, in-review, stable, retired).
datasetYesURL of the open-data document the answer was read from.
licenseYesLicence of the data (CC BY 4.0, attribution required).
profileYes
versionYes
evidenceYes
examplesYesIllustrative example observations, valid against the observation schema.
mappingsYesIllustrative mappings, not a claim of conformity.
patternsYes
layerNameYes
objectiveYes
referencesYes
dataVersionYesBody of Knowledge version of the data.
observationYesWhat an observation of the control records; null until the control is specified.
profileInfoYes
failureModesYes
verificationYes
openQuestionsYesQuestions a technical reviewer should settle.
reviewerStatusYesTechnical review status; open means no one has reviewed it yet.
failureResponseYes
secondaryLayersYes
enforcementPointsYes
observationSchemaYesSchema of a control observation record.
implementationNotesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is fully covered and the bar is low. The description's one genuinely additive behavioral note is that the returned artifact is "a draft control specification, open for technical review" — a useful caveat about content maturity. The rest of the sentence merely enumerates return fields, which the existing output schema already carries.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The verb, resource and identifier forms are correctly front-loaded. But the opening sentence is a single sprawling run-on that then re-lists a dozen record sections already documented by the output schema, so a large share of the text does not earn its place.

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?

With a full output schema and complete annotation coverage, the definition does not need to explain return values, yet it spends most of its length doing so. What is missing is the operational edge cases: behavior on an unknown id, whether title matching is exact or fuzzy, and whether errors are raised or returned.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, and the description earns above that by clarifying what the single parameter actually accepts: case-insensitive ids, a short form with the prefix dropped ("EVAL-002"), a concrete example ("AIGE-CTL-EVAL-002"), and URLs or titles as alternatives. This resolves real ambiguity in what "id" means beyond the terse schema text.

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?

Opens with a specific verb and resource ("Get one reference control") and scopes it by three accepted identifier forms, which separates it from get_obligation/get_pattern/get_term on resource and from list_controls on cardinality. The remainder of the description degrades into an undifferentiated field dump that blurs rather than sharpens the purpose, and no sibling is named 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 identifier forms (stable id, page/JSON URL, or title) imply how to invoke it, and "one" implies it is the single-item fetcher. However, nothing says when to reach for this versus list_controls or search_bok, and there is no guidance on what to do if the id is unknown or ambiguous.

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.