Skip to main content
Glama

Read StewAI Recipe Details

get_recipe_details
Read-onlyIdempotent

Read the authorized published details and executable contracts for one opaque recipe reference. Follow next_cursor until null. This tool never executes a recipe.

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": {
      "recipe_ref": "<recipe_ref>"
    },
    "name": "get_recipe_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNo
recipe_refYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds real context on top: results are limited to "authorized" published data, output is paginated via next_cursor, and the reference is treated as opaque. The explicit "never executes" boundary reinforces rather than contradicts the annotations.

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?

Three short sentences, each carrying a distinct load: what is returned, how to paginate, and what the tool will not do. No filler and no repetition of the name.

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 an output schema present, return shape need not be described, and the read-only annotations cover safety. The description supplies scope, authorization, and pagination, so it is adequate for a 2-param read tool; only sibling routing guidance is thin.

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 coverage is 0%, yet the description conveys that recipe_ref is an opaque token (do not parse or construct it) and that cursor drives pagination until next_cursor is null. That covers the semantics of both parameters, leaving only format/length details to the schema.

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+resource: "Read the authorized published details and executable contracts for one opaque recipe reference." That distinguishes it from build/preview style siblings by scope (published, per-reference), though it does not name any sibling to route away from.

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?

Gives pagination usage ("Follow next_cursor until null") and one exclusion (never executes a recipe), but no guidance on when to pick this over the many other get_recipe_* getters such as get_recipe_build_contracts or get_recipe_preview.

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