Skip to main content
Glama

List Automations

mcp_recipe_list
Read-onlyIdempotent

The company's shoot automations (and other automations to copy).

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": {
      "board_id": "<board_id>"
    },
    "name": "mcp_recipe_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
queryNoName search.
board_idYesThe open Shoot Board's board_id, from Open Shoot Board or your context.
items_per_pageNo
include_automationsNoAlso list automations (read/copy only).
include_definitionsNoAlso return each listed automation's live graph (the cards that draw its steps).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds only a loose scope statement and says nothing about pagination, return shape, or the effect of the include_* flags beyond what the schema already notes.

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

Conciseness2/5

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

It is short, but this is under-specification rather than conciseness: a single sentence fragment that omits the core action verb, so it does not front-load a usable statement of what the tool does.

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

Completeness2/5

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

For a paginated, filterable listing tool with six parameters and no output schema, the description is far too thin. An agent cannot tell what is returned, how paging behaves, or how this differs from the other mcp_recipe_* tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Six parameters at 67% schema coverage, and the description contributes no meaning for any of them — not the required board_id, the query search, paging, or the include_automations/include_definitions toggles. It neither supplements the documented params nor compensates for the undocumented ones.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a noun fragment — 'The company's shoot automations (and other automations to copy)' — with no verb stating that it lists them. It names the resource but the parenthetical 'and other automations to copy' muddies scope, and it never distinguishes this from siblings like mcp_recipe_copy, mcp_recipe_history, or mcp_recipe_open.

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?

There is no explicit when-to-use or when-not-to-use guidance. The phrase 'to copy' faintly implies this feeds mcp_recipe_copy, but the agent must infer that; no alternative or condition is named.

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