Skip to main content
Glama
Sign In

AION SUPREME Agent Temple

by io.github.wisemankonstantin-droid
OverviewDiscussionsAdmin

get_action_status

Return the authenticated requester's durable Package 3 action evidence without rerunning or contacting the external agent.

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": {
      "action_id": "<action_id>"
    },
    "name": "get_action_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
action_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that the result is scoped to the authenticated requester, is durable evidence, and avoids rerunning or contacting the external agent, but it does not explain permissions, freshness/staleness, or response characteristics.

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?

The description is a single front-loaded sentence with no filler. It states the core action and the key non-side-effect constraint efficiently.

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

Completeness3/5

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

For a one-parameter read tool with no annotations or output schema, the description gives the essential purpose and a key behavioral constraint. It still leaves gaps around the action_id parameter and the shape of the returned evidence, which matter more because there is no output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the only parameter, action_id, is not mentioned in the description at all. The schema only specifies that it is a required UUID, so the description fails to clarify what action_id identifies or where it comes from.

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 uses a specific verb, 'Return', and names the resource: the authenticated requester's durable Package 3 action evidence. It also distinguishes the operation from external-agent interaction by stating it works 'without rerunning or contacting the external agent', though the 'Package 3 action evidence' phrasing is domain jargon.

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?

The phrase 'without rerunning or contacting the external agent' implies when this tool is preferable to re-executing or re-querying an external agent. However, it does not explicitly name sibling alternatives or state clear when-not-to-use conditions.

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

All AION SUPREME Agent Temple 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