Skip to main content
Glama
Sign In
Aureon MCP

Aureon MCP

Official
by buildaureon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

aureon_get_receipt_verification_flow

Reads execution receipts and returns their verification flow, optionally for one execution ID or the five most recent.

Instructions

Read receipt → verification flow for execution receipts

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "aureon_get_receipt_verification_flow"
  }
}

Input Schema

NameRequiredDescriptionDefault
executionIdNoFilter to one execution id (omit for five most recent)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.16

TDQS

C2.5/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. The word 'Read' weakly implies a read-only operation, but it says nothing about what the flow contains, whether it is static documentation or live state, auth requirements, or limits. This is a significant gap for an unannotated tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence, which is well-sized, but the brevity reflects under-specification rather than disciplined conciseness. It is front-loaded only in the trivial sense that it is one phrase.

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

Completeness2/5

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

For a read tool with no output schema and no annotations, the description should explain what the returned 'flow' actually is (steps, stages, status). It omits this entirely, leaving the agent unable to predict the response shape or confirm it is the right tool.

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 schema fully explains the single executionId parameter ('Filter to one execution id (omit for five most recent)'). The description adds no parameter meaning beyond what the schema provides, so baseline 3 applies.

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

Purpose3/5

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

The phrase 'Read receipt → verification flow for execution receipts' names a resource (receipt verification flow) but largely restates the tool name rather than explaining what the tool actually returns or does. It does not distinguish itself from siblings such as aureon_validate_receipt or aureon_run_receipt_verification_demo. Purpose is only vaguely inferable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives. With sibling tools like aureon_validate_receipt and aureon_run_receipt_verification_demo present, the agent gets no signal about which to pick. No exclusions or context are given.

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

Deploy Server

Other Tools