Skip to main content
Glama

Secure Autonomous Register

List controls

list_controls
Read-onlyIdempotent

The Register's controls (the safeguards that would interrupt the failures it records), each with how many published cases record it as failed, absent or held.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_controls"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed world, so safety needs no restating. The description adds genuine substance beyond that: each control is returned accompanied by aggregate counts of how many published cases record it as failed, absent or held, which tells the agent the shape and analytic value of the response.

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 tightly packed sentence with no filler, and the parenthetical definition is placed where it resolves ambiguity immediately. It is slightly awkward that the sentence opens on a noun phrase with no verb, leaving the action to the title, but nothing is wasted.

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 parameters and no output schema, the description carries the burden of explaining the return, and it does so by describing the per-control failure/absence/holding counts. Minor gaps remain: no indication of ordering, result volume, or whether counts are scoped to published cases only in a time window.

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?

The tool takes no parameters and the input schema is empty, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly spends no words on arguments and instead characterizes the return payload.

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 a specific resource — the Register's controls — and parenthetically defines what a 'control' is (safeguards that would interrupt recorded failures), so the agent knows exactly what entity is returned. The verb comes only from the title 'List controls'; the description itself is a noun phrase. It does not differentiate from the sibling get_control (single-record retrieval).

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?

Usage is implied rather than stated: an enumeration tool with zero parameters is largely self-selecting when an agent wants the full control inventory. There is no explicit when-to-use, no when-not-to-use, and no named alternative such as get_control for drilling into a single control or search_cases for case-level records.

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