Skip to main content
Glama

Operator stacks

get_operator_stack
Read-only

Look up operator stacks in The Stack Index. Pass operator to get one operator's full stack by layer with their episode. Pass tool to get every operator who runs that tool, what they use it for, and every displacement on the record (what it replaced, what replaced it). Use when the user asks what a specific operator runs, or who uses a specific tool and what alongside it.

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": "get_operator_stack"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolNo
operatorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/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 lookup. The description adds useful behavior beyond that by explaining what each query mode returns, including layer stacks, episodes, tool usage, and displacement records. It does not cover permissions, rate limits, or pagination, but those are less critical for a read-only lookup.

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?

The description is three tight sentences, front-loaded with the core action and followed by the two parameter modes and usage triggers. Every sentence adds useful information without repetition.

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?

For a read-only lookup tool with no output schema, the description explains the return content for both query modes and covers the key parameters. It leaves minor gaps around parameter combinations and edge-case behavior, but is otherwise complete enough for an agent to invoke it correctly.

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 description coverage is 0%, so the description carries the full burden of explaining parameters. It clearly defines what the operator parameter returns and what the tool parameter returns. It does not explain what happens when both are provided, when neither is provided, or whether the parameters are mutually exclusive.

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: 'Look up operator stacks in The Stack Index,' and clearly explains the two lookup modes. It does not explicitly differentiate itself from sibling tools such as list_operators, so it stops short of 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear triggers: use when the user asks what a specific operator runs, or who uses a specific tool and what alongside it. It does not state exclusions or name alternative tools, which keeps it from a 5.

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