Aetherya

Seal a prediction before the outcome is known

aetherya_seal_prediction

Lock a prediction (a creative comparison ranking, a video analysis, a study or a manual payload) with a SHA-256 hash and timestamp, so it can later be compared with what really happened. Pass source_id to seal a finished simulation, or payload for a manual prediction. Returns the id, hash and sealed payload.

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": {
      "source_kind": "<source_kind>",
      "label": "<label>"
    },
    "name": "aetherya_seal_prediction"
  }
}

Input Schema

Name	Required	Description
`label`	Yes	Short name, e.g. 'Spring campaign, 3 creatives'.
`payload`	No	Prediction content; required for 'manual'.
`source_id`	No	Id of the comparison, video analysis or study run.
`source_kind`	Yes	What is being sealed.

Output Schema

Name	Required	Description	Default
`id`	No
`source`	Yes
`payload`	No
`createdAt`	No
`payloadSha256`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 19, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive write, so the description only needs to add context. It does: the record is tamper-evident (hash + timestamp) and 'locked' for later comparison, and it discloses the return shape. It stops short of stating immutability guarantees, permission needs, or idempotency of repeated seals.

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?

Three tight sentences, with the core purpose and the input-routing rule front-loaded. The trailing 'Returns the id, hash and sealed payload' is mildly redundant given the output schema, but it is one short clause and not disruptive.

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 annotations carrying the safety profile and an output schema covering return values, the description supplies what an agent needs to invoke this correctly, including the source_id vs payload decision. It is only slightly incomplete in not tying the tool to the later verify step or noting whether sealing is irreversible.

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 coverage is 100%, so all four parameters, including the source_kind enum, are already documented in the schema, and the schema already notes payload is 'required for manual'. The description restates the source_id/payload split without adding syntax, format, or validation detail beyond it, so 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?

States a specific verb and resource ('Lock a prediction ... with a SHA-256 hash and timestamp') and enumerates the accepted payload kinds (creative comparison ranking, video analysis, study, manual payload). It is clearly distinguishable from siblings like aetherya_verify_prediction and aetherya_record_outcome, which cover the later comparison stage.

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?

Explicit conditional routing is given: 'Pass source_id to seal a finished simulation, or payload for a manual prediction.' This tells the agent how to select inputs, but it never names the complementary siblings (verify_prediction, record_outcome) or says when sealing is not the right action.

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?