Skip to main content
Glama

List mechanisms

list_mechanisms
Read-onlyIdempotent

List entries with identifier, name, layer, kind and review state, optionally by layer and review state. The default lists every entry; with review=accepted the response states how many entries in review are not shown.

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_mechanisms"
  }
}

Input Schema

NameRequiredDescriptionDefault
layerNoLayer: core, social, extension, corpus or crisis_type.
reviewNoReview state filter (versions 1.3.0 and later): all (default), accepted or in_review. The default covers every published entry and each result states its review state; entries in review are published and usable. With accepted the response says how many more matching entries are in review.
versionNoRegistry version, for example "1.4.1" (a leading "v" is accepted). Default: the latest published version (1.4.1). Available: 1.0.0, 1.1.0, 1.2.0, 1.3.0, 1.3.1, 1.4.0, 1.4.1.

Output Schema

NameRequiredDescriptionDefault
noteNo
scopeNoScope of the registry: what the entries are and are not.
totalYes
reviewNo
entriesYes
versionYes
returnedYes
in_review_not_shownNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / version / description
      Previous value: -"Registry version, for example \"1.4.0\" (a leading \"v\" is accepted). Default: the latest published version (1.4.0). Available: 1.0.0, 1.1.0, 1.2.0, 1.3.0, 1.3.1, 1.4.0."New value: +"Registry version, for example \"1.4.1\" (a leading \"v\" is accepted). Default: the latest published version (1.4.1). Available: 1.0.0, 1.1.0, 1.2.0, 1.3.0, 1.3.1, 1.4.0, 1.4.1."
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already establish that this is a safe, read-only, idempotent, non-destructive listing operation. The description adds useful behavioral detail: the default returns every entry, while review=accepted suppresses in-review entries and reports how many were omitted.

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

Conciseness5/5

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

Two compact sentences with no wasted wording. The default behavior and the review=accepted exception are front-loaded and easy to scan.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The schema is fully documented, annotations cover safety semantics, and an output schema exists, so return format need not be explained. The description supplies the remaining useful behavior about default listing and accepted-only filtering.

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 100%, so the schema already documents layer, review, and version thoroughly. The description reinforces the review=accepted behavior, but it adds little parameter meaning beyond what the schema provides.

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 states a specific verb and resource: it lists entries and names the returned fields (identifier, name, layer, kind, review state). It is clear what the tool does, but it does not explicitly distinguish itself from siblings such as search_mechanisms or list_versions.

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?

It explains the default behavior and the effect of review=accepted, which gives implied guidance on filtering. However, it never says when to use this tool instead of search_mechanisms, get_mechanism, or list_versions.

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.