Aetherya

Estimate the cost of a simulation before running it

aetherya_estimate

Read-only

Quote how many simulation sessions a run would cost, and roughly what share of your plan it would consume, before committing to it. Free — this never starts a simulation. Use it to size an audience or shorten a study when headroom is tight.

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": {
      "kind": "<kind>"
    },
    "name": "aetherya_estimate"
  }
}

Input Schema

Name	Required	Description
`kind`	Yes	What you are about to run.
`depth`	No	Engagement depth. Cost multiplier: 1x / 2x / 4x.
`method`	No	Required when kind is 'study' — the research method id.
`variants`	No	Number of copy variants, for a copy test.
`questions`	No	Number of survey questions.
`audience_size`	No	Simulated respondents / audience size.

Output Schema

Name	Required	Description
`kind`	Yes
`note`	No
`source`	Yes
`sessions`	Yes	Estimated simulation sessions, or null when Aetherya cannot quote this kind up front. Never treat null as zero — read `note` instead.
`breakdown`	No
`planImpact`	No
`eurEquivalent`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 19, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the no-mutation profile is covered. The description still adds two facts not in structured data: the call is free and it never starts a simulation, which matters because an agent might otherwise avoid a cost-checking tool on quota grounds. No rate/idempotency detail.

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, front-loaded with the core outcome (session cost + plan share), then the free/no-execution guarantee, then the use case. Every clause carries information and nothing is repeated.

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?

An output schema exists, so return values need not be explained, and all six parameters are documented in-schema. The description covers purpose, cost profile, and when to use; only sibling routing and any edge-case caveats are absent, which is a minor 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 the depth enum multipliers and the 'method required when kind is study' rule are already documented in-schema. The description only obliquely gestures at levers ('size an audience', 'shorten a study'), which maps loosely to audience_size and study length, so baseline 3 applies.

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?

Specific verb and resource: it 'quotes' the simulation-session cost of a run and the share of plan consumed, and it is explicitly pre-commitment ('before committing to it'). That differentiates it from aetherya_run_study / aetherya_plan_study without naming them, so it is clear but lacks explicit sibling routing.

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?

Gives concrete when-to-use context: 'Use it to size an audience or shorten a study when headroom is tight,' plus the pre-run timing cue. No exclusivity rules or named alternatives (e.g. 'call this instead of run_study when uncertain'), so it stops short of a 5.

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

All Aetherya tools Inspect

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

Need Help?