Skip to main content
Glama

AI-Agent-ready capital markets disclosure news per issuer — Allooloo

Create Order Intent

create_order_intent

An order intent for a paid read (the full row or the delta): returns the x402 terms for mcp.getissuernews.ai and the intent id to carry into the paid call. Nothing is sold but the read.

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": {
      "issuer": "<issuer>"
    },
    "name": "create_order_intent"
  }
}

Input Schema

NameRequiredDescriptionDefault
scopeNodelta
sinceNo
issuerYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/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, and it does disclose the key trait: 'Nothing is sold but the read,' making clear this is a non-charging intent step rather than a purchase. It omits whether intents expire, whether creation is idempotent, and any auth or payment-protocol requirements surrounding the x402 terms. Output schema exists, so return values need not be explained.

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?

Two compact sentences with the subject (order intent for a paid read) front-loaded and the return value immediately after. Minor awkwardness from the elliptical opening fragment and the dangling 'Nothing is sold but the read,' but nothing is wasted.

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?

The presence of an output schema removes the need to describe returns, and the description does convey the tool's role in a paid-read workflow. However, for a 3-parameter tool with zero schema coverage and no annotations, the undefined 'since' and 'issuer' parameters and absent intent-lifecycle details leave real gaps.

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 for three bare parameters. It partially does for scope by naming the two modes ('the full row or the delta'), but 'since' and 'issuer' get no explanation at all, leaving a required parameter and a nullable filter undefined anywhere in the definition.

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 names the resource (a paid read, either the full row or the delta) and the concrete output (x402 terms for mcp.getissuernews.ai plus the intent id to carry into the paid call). That is specific enough to separate it from siblings like get_row or get_delta, which appear to fetch data directly. It lacks an explicit verb ('creates an intent'), opening on a bare noun phrase.

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?

Usage is only implied: the mention of an 'intent id to carry into the paid call' signals this is a prerequisite step preceding a paid read. There is no explicit statement of when to use this versus claim_row/get_row, no prerequisites, and no when-not guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources