Skip to main content
Glama

Estimate a StewAI Recipe Run

estimate_recipe_run
Read-onlyIdempotent

Estimate one previewed recipe without starting it. Return historical charges, fees, wallet balance, admission status, and the safety ceiling when one can be calculated.

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>",
      "inputs": "<inputs>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "estimate_recipe_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputsYes
recipe_refYes
idempotency_keyYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior. The description reinforces that no run is started and notes the safety ceiling is conditional, but it otherwise lists outputs already covered by the output schema and adds little about auth or side effects.

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?

Two sentences, front-loaded with the core action and followed by the return values. No filler or redundant wording.

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

Completeness3/5

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

The tool has three required parameters, a nested inputs object, and no schema descriptions, so the description should carry more parameter guidance. Annotations and the output schema cover safety and returns, but an agent still lacks enough detail on inputs and idempotency_key.

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?

Schema description coverage is 0% across three required parameters. The description adds only that the recipe must be 'previewed'; it does not explain the recipe_ref format, the inputs object's expected keys or values, or the role of idempotency_key, leaving most parameter meaning undocumented.

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

Purpose5/5

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

The description uses the specific verb 'Estimate' with the resource 'one previewed recipe' and explicitly distinguishes it from starting the recipe. The scope ('one', 'previewed') helps an agent tell it apart from run_recipe.

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 says to use the tool on a previewed recipe and that it does not start the recipe, which implicitly excludes execution. However, it does not explicitly name run_recipe or other alternatives, nor does it state the prerequisites for obtaining a 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