Skip to main content
Glama

Estimate workflow cost

estimate_workflow
Read-only

Credits a workflow run would cost with these inputs, without running it. Validates the inputs against the workflow's form. Media inputs take one asset id from upload_asset or an earlier job, a public https URL or a data: URI. Also returns available_credits, the organization's spendable balance.

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": {
      "slug": "<slug>"
    },
    "name": "estimate_workflow"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes
inputsNo
projectNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds real context on top: it validates inputs against the workflow's form, specifies the acceptable media input forms (asset id, public https URL, data: URI), and discloses that 'available_credits' is returned alongside the estimate. It stops short of describing what happens when validation fails.

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?

Content is dense and front-loaded with the core purpose, and every clause carries information (dry-run, validation, media formats, balance). The awkward line-broken formatting and the clipped opening phrase slightly hurt readability.

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, the description needn't enumerate return fields, and it still usefully calls out 'available_credits'. For a read-only estimator the main missing element is guidance on invalid inputs and on sibling 'estimate_cost'.

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 0% across three parameters, so the description must compensate. It does explain the 'inputs' object well, including the accepted media reference formats and that it is validated against the workflow form, but 'slug' and 'project' are never described, leaving a meaningful gap.

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 states a specific verb and resource: it returns the credit cost a workflow run would incur with given inputs, explicitly without executing it. It also notes input validation and the credit balance in the response. It does not, however, distinguish itself from the sibling 'estimate_cost', so an agent must infer the difference.

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?

Usage is implied rather than stated: 'without running it' signals a pre-flight/dry-run check, and it points at upload_asset (or an earlier job) as the source of asset ids. There is no explicit when-to-use versus 'estimate_cost' or 'run_workflow', and no exclusion guidance.

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