Skip to main content
Glama

Operators on the record

list_operators
Read-only

List the operators on the record in The Stack Index, with their company, episodes and how many tools they named. Filter by layer, by tool, or by show. Use when the user asks who is in the index, who to learn from in a layer, or which operators run a tool. Returns operator names and slugs.

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

Input Schema

NameRequiredDescriptionDefault
showNo
toolNo
limitNo
layer_idNoOne of the eight layers of revenue architecture.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare read-only and closed-world behavior. The description adds useful detail beyond that by naming the returned fields and the available filter dimensions, though it does not explain ordering, pagination, or limit behavior.

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 four tight sentences, front-loading what is listed, then filters, then usage scenarios, then return values. Every sentence contributes and there is no filler.

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 output schema and low parameter description coverage, the description does a good job stating return fields and main filters. The main gap is the unexplained limit parameter and lack of default or pagination context.

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 only 25%, so the description should compensate more. It explains that results can be filtered by layer, tool, or show, but it omits any explanation of the limit parameter and does not clarify the show enum values or tool semantics.

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 gives a specific verb and resource: list operators in The Stack Index, including company, episodes, and tool counts. It is clear what the tool does, though it does not explicitly distinguish itself from siblings such as get_operator_stack or list_playbooks.

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 states clear usage contexts: when the user asks who is in the index, who to learn from in a layer, or which operators run a tool. It lacks explicit when-not guidance or named alternatives, but the triggering scenarios are concrete.

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