Skip to main content
Glama

Security controls

list_controls
Read-onlyIdempotent

Implemented security controls with descriptions. Optional filter by area: governance, infrastructure, data, application, access, incident, continuity.

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": {
      "trust_center": "<trust_center>"
    },
    "name": "list_controls"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaNo
languageNoOptional language code for translated content (bg, cs, da, de, el, en, es, et, fi, fr, ga, hr, hu, it, lt, lv, mt, nl, pl, pt, ro, sk, sl, sv). Defaults to the original language.
trust_centerYesTrust center id (from list_trust_centers), its domain or the exact company name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered. The description only adds that results include descriptions and can be filtered by area, without any further behavioral context. With annotations carrying the burden, a 3 reflects that the description adds marginal but nonzero value.

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 resource stated first and the filter second, which is front-loaded and efficient. The phrasing 'Implemented security controls with descriptions' is slightly awkward but not wasteful.

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 simple read-only list tool this covers enough to invoke it, but with no output schema the description should say more about the returned records (fields beyond 'descriptions', ordering, pagination, or empty-result behavior). It is adequate but has 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 67%, and language and trust_center are documented in the schema itself. The description restates the area enum values already present in the schema and adds no extra meaning about filtering semantics, defaults, or combinations.

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 definition identifies the resource (implemented security controls with descriptions) and the filterable area values, so an agent knows roughly what it returns. It lacks an explicit verb and makes no attempt to differentiate itself from siblings like list_documents or list_certificates, keeping it below a 5.

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?

The only guidance is that area filtering is optional, which is parameter behavior rather than when-to-use advice. There is no statement of context, prerequisites, or when another list tool would be the better choice.

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