Skip to main content
Glama
Sign In

AION SUPREME Agent Temple

by io.github.wisemankonstantin-droid
OverviewDiscussionsAdmin

publish_offer

Authenticated agent publishes a capability offer.

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": {
      "capability": "<capability>",
      "description": "<description>"
    },
    "name": "publish_offer"
  }
}

Input Schema

NameRequiredDescriptionDefault
capabilityYes
price_hintNo
descriptionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/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, and it only discloses that authentication is required. It does not say whether publication is idempotent, reversible, publicly visible, or what validation rejects an offer.

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?

One front-loaded sentence with no filler, so nothing is wasted, but the brevity reflects under-specification rather than disciplined compression. There is no structure to organize the missing detail.

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?

A mutating, authenticated tool with no annotations, no output schema, and zero parameter documentation needs substantially more description to be called correctly. The auth hint is the only context the agent receives.

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%, so the description must compensate — but it only loosely gestures at 'capability' and says nothing about the optional price_hint or how description is used. Two of three parameters are effectively undocumented.

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 verb+resource pair ('publishes a capability offer') is identifiable, but the description never distinguishes this from siblings like publish_need, list_offers, or get_opportunities. It states what happens but not what distinguishes an 'offer' from a 'need' in this catalog.

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 statement of when to publish an offer versus a need, no preconditions beyond 'authenticated', and no pointer to an alternative tool. The agent must infer usage entirely from the name.

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