Skip to main content
Glama

AINDEX

Approve or decline a proposal

answer_agent_proposal
Destructive

Approve or decline one trade an agent proposed (list_agent_proposals gives the ids). Approve queues it: AINDEX's agent service plans it again, simulates it, checks it with the safety net (money goes only to the agent's wallet, you or a protocol AINDEX knows), and only then signs and sends it from the agent's wallet or Lighter account. Decline drops it. Needs an access key that may act. Confirm with the person before approving.

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": {
      "agent": "<agent>",
      "proposal": "<proposal>",
      "answer": "<answer>"
    },
    "name": "answer_agent_proposal"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentYes
answerYes
proposalYesThe proposal's id, from list_agent_proposals.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Goes well beyond the annotations by describing the full approval pipeline: re-planning, simulation, a safety net restricting payouts to the agent's wallet or known recipients, then signing and sending from the agent's wallet or Lighter account, versus a decline that simply drops the proposal. Annotations already flag destructive and open-world behavior, and the description reinforces that with the actual consequence. It stops short of stating what is returned on success or how failures surface.

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?

Front-loads the action and the effect, with the id-sourcing hint and the confirmation requirement placed early. It is dense but nearly every clause carries operational meaning; only the parenthetical safety-net details could be trimmed slightly.

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

Completeness4/5

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

For a destructive, non-idempotent mutation with no output schema, the description covers prerequisites, side effects, and the confirmation requirement adequately. Missing are the return value or status on approval and error behavior, which would matter for an agent deciding whether to retry.

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

Parameters4/5

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

Schema coverage is only 33%, so the description must compensate, and it largely does: it explains that the proposal id comes from list_agent_proposals and gives concrete meaning to the approve/decline enum by describing the downstream effect of each. The agent parameter is only implicitly characterized through references to the agent's wallet and access key requirements.

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

Purpose5/5

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

States a specific verb pair (approve or decline) and resource (one trade an agent proposed), and contrasts itself with list_agent_proposals, which supplies the ids. An agent can distinguish this from the listing sibling without reading either schema.

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 clear context: fetch ids from list_agent_proposals, requires an access key that may act, and mandates confirming with the person before approving. It does not spell out when an agent should decline versus escalate, but the prerequisites and the sibling pointer are explicit.

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