Skip to main content
Glama

Meta Council

by com.meta-council
OverviewDiscussionsAdmin

Estimate Cost

estimate_cost
Read-onlyIdempotent

Estimate what a panel or saved workflow would cost before running it: returns a per-agent/per-step price breakdown, the total for the requested number of runs, your remaining quota and platform credit, an honest list of any models the platform could not price, and a go/no-go decision. Reserves nothing, charges nothing, starts nothing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindYesWhat to price: a council panel or a saved workflow.
runsNoHow many runs to price (default 1).
modelNoOptional single model override applied to every agent or step. A model absent from the pricing catalog is reported in unpriced_models rather than silently priced as the default.
panelNoPanel slug when kind is 'council' (default: 'default').
workflowNoWorkflow slug — required when kind is 'workflow'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": false,
-  "properties": {
-    "text": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "text"
-  ],
-  "type": "object"
-}New value: +null
  2. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already indicate read-only, idempotent, and non-destructive. The description strengthens this by explicitly guaranteeing zero resource reservation, zero charges, and zero execution start, and adds a behavioral commitment to honestly report models the platform could not price. No contradiction with 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?

Two tightly packed sentences: the first front-loads purpose and enumerates return items, the second delivers the side-effect guarantee. Every clause earns its place with no filler or repetition of schema details.

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

Completeness5/5

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

With no output schema, the description carries the burden of explaining return value contents: breakdown, total, quota/credit, unpriced models, and go/no-go decision. Combined with the 100%-covered schema and clear annotations, an agent has everything needed to invoke it correctly. No meaningful gap.

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 100%, and every parameter carries its own description, so the tool description is not required to re-document parameters. It adds only indirect semantics by tying 'requested number of runs' to the runs parameter and 'panel or saved workflow' to kind, which mostly repeats schema text. Baseline 3 applies.

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?

Clear verb 'Estimate' plus explicit resource 'panel or saved workflow' and timing 'before running it'. Distinguishes itself from run_council/run_workflow by emphasizing it is a pre-run cost preview with no side effects. No ambiguity about its role among siblings.

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?

The phrase 'before running it' and the triple negative 'Reserves nothing, charges nothing, starts nothing' give an agent a clear decision rule for choosing this over execution tools. However, it does not explicitly name sibling tools like run_council or run_workflow, nor state conditions when not to use it, so it stops short of a full 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Meta Council toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources