Skip to main content
Glama

Ask apex

ask_apex

Ask Apex runs one plain task on our best matching tool and charges that tool price plus $0.001. The listed price is the minimum, for a call with no task. If none of our tools fit, an outside x402 tool is used only when its delivery score is 80 or higher: you pay us that price plus 10 percent first, and we never pay the outside tool more than you already paid. Nothing is signed on your behalf. $0.002 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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": {
      "task": "<task>"
    },
    "name": "ask_apex"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskYesplain task, 3 to 600 characters
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and mostly succeeds: it discloses pricing ($0.002/call, minimum charge for an empty call), the 10 percent markup on external routing, the '$0.001 over tool price' premium, accepted payment rails, and 'Nothing is signed on your behalf.' It does not say what happens if no internal or external tool qualifies, or whether a failed routing still charges.

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?

The pricing model is mentioned early, but the body is a run-on chain of clauses with dropped articles ('charges that tool price', 'the minimum, for a call with no task') and one muddled line: 'we never pay the outside tool more than you already paid.' The critical two-call protocol is buried in the final sentence instead of being front-loaded.

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 2-parameter paid routing tool with no annotations and no output schema, the payment and pricing behavior is well covered. Missing is what the tool returns (the matched tool's result, a routing record, or a price quote on the first call) and what occurs on no-match or payment failure — both material for an agent deciding to spend money.

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 both `task` (3-600 chars) and `payment` (signed x402 payload) are already documented in the schema, setting a baseline of 3. The description adds the two-step handshake meaning of `payment` beyond the schema's phrasing, but does not explain task phrasing, matching behavior, or what makes a task unroutable.

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?

Opens with a specific verb and resource: 'runs one plain task on our best matching tool,' which makes clear this is a router/meta-tool rather than a direct operation. It does not name or contrast any sibling (e.g., arc_agent_search), so an agent must infer from the name alone that this is an aggregator, but the core purpose is unambiguous.

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?

Gives an explicit operational flow: 'Call once without `payment` for the terms, sign them with your own wallet, call again with `payment`,' and states the fallback condition for outside x402 tools (delivery score >= 80). It lacks guidance on when to choose this over a direct sibling tool, which is the only real gap.

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