Skip to main content
Glama

AI Agent Audit and Action Review

Check checkout for a 1 EURC agent action review

get_agent_action_review_checkout
Read-only

Check the EURC account and get the checkout URL. If setup is required, optionally supply a public payer address and an explicitly authorized SOL budget to receive an unsigned setup transaction. This tool never signs, broadcasts or charges anything. A review is purchased separately via POST /v1/review.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_agent_action_review_checkout"
  }
}

Input Schema

NameRequiredDescriptionDefault
setupNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds substantive context beyond them: nothing is signed, broadcast, or charged, and the returned setup artifact is explicitly unsigned. That resolves the natural tension an agent would feel about a read-only tool producing a transaction. It stops short of describing error conditions or what the EURC account check actually validates.

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?

Four sentences, each carrying distinct payload, with the primary action front-loaded ahead of the conditional setup branch. The safety disclaimer is well placed after the setup mechanics. Minor redundancy between "explicitly authorized" and "never charges anything," but no filler.

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?

With one optional nested parameter and no output schema, the description does the work that structured fields cannot: it names the two things returned (checkout URL, or an unsigned setup transaction). What is missing is the price context implied by the title (1 EURC) and any statement about failure modes when the EURC account is unfunded.

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 description coverage is reported as 0% at the top level, so the description must compensate for the single optional nested "setup" object — and it does, naming the public payer address and the authorized SOL budget and framing them as opt-in only when setup is required. However, it adds little on the budget's semantics (one-time cost ceiling, reserve plus fee) that the nested schema fields do not already state, so this is baseline-plus rather than a real gain.

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?

States a specific verb and resource: "Check the EURC account and get the checkout URL," which is concrete enough that an agent can tell this is the pre-purchase checkout step. It never differentiates itself from the sibling tools (get_agent_action_review_service, read_agent_action_review), so the reader must infer the boundary from the name alone.

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 real conditional guidance: the setup object is supplied only "if setup is required," and only with an explicitly authorized SOL budget. It also draws a hard exclusion — "A review is purchased separately via POST /v1/review" — telling the agent this tool does not complete the purchase. No explicit routing versus the sibling review tools, which keeps it below a 5.

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