Skip to main content
Glama

List StewAI Recipe Builds

list_recipe_builds
Read-onlyIdempotent

List recent private recipe builds owned by the authenticated creator.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
cursorNo
include_archivedNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, non-destructive, idempotent, closed-world), so the bar is lower. The description still adds real scoping context the annotations cannot express: results are limited to private builds owned by the calling creator, which is a meaningful access boundary. It does not explain archived behavior or ordering, but for an annotated read-only list that is a minor omission.

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?

A single front-loaded sentence with no filler, so it is efficient. Brevity here borders on under-specification rather than excess, but the sentence itself earns its place.

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?

A list tool with three undocumented parameters, with an output schema to handle return values. Missing are key details such as the default and maximum page size behavior, cursor usage for pagination, whether archived builds are included by default, and result ordering. For a paginated list endpoint, those gaps are material.

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?

All three parameters (limit, cursor, include_archived) have zero description coverage in the schema, and the description never mentions them. Only a hint that results are capped is implicit; "recent" gestures at default ordering, and include_archived raises the question of whether archived builds are excluded by default, which is not answered. Cursor pagination semantics are entirely undocumented.

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?

States a specific verb and resource ("List ... recipe builds") plus scope qualifiers: recent, private, and owned by the authenticated creator. That scope meaningfully separates it from single-item siblings like get_recipe_build, but no sibling is named so the differentiation is implicit.

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?

"recent" and "owned by the authenticated creator" imply when the tool applies, and the sibling list shows many other list_* build sub-resources, so an agent can infer this returns builds rather than nodes/activities. However, there is no explicit when-to-use, no exclusion of alternatives, and no mention of when to prefer get_recipe_build for a specific build.

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