Skip to main content
Glama

audit.domains - Domain Valuation

Buy an appraisal: enrolled agent card ($5)

buy_appraisal_agent_card
DestructiveIdempotent

RAIL: AGENT CARD. Buy a fresh appraisal of one domain, computed on this server, for $5, charged unattended to a card your operator enrolled once for you (card-agent-1). No person is present at purchase time and no payment page opens: the charge runs against the enrolled card, inside the grant and the consent caps your operator set. Requires your agent token on this MCP connection, plus grantId and cardRef from your operator. Pass a stable operationId of your own: repeating this call with the same operationId and the same request returns the stored charge and never charges twice; the same operationId with a different request is refused operation_id_conflict. Returns the appraisal in the same call when the engine delivers at once; otherwise poll appraisal_card_order_status with the same operationId. A charge the engine cannot deliver is refunded automatically and in full. Not this rail when a person will pay at a checkout page: buy_appraisal is the human card rail (same $5, orderId + orderToken). Not this rail when your operator funded a prepaid balance instead of enrolling a card: purchase_appraisal draws $0.03 from that balance.

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": {
      "domain": "<domain>",
      "grantId": "<grantId>",
      "cardRef": "<cardRef>",
      "operationId": "<operationId>"
    },
    "name": "buy_appraisal_agent_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesThe domain to appraise, e.g. brightcargo.com.
cardRefYesThe enrolled card handle (acr_...) from enrollment.
grantIdYesThe purchase grant id your operator issued you.
maxSpendUsdNoYour hard ceiling for this charge. Defaults to the price, $5.
operationIdYesYour idempotency key for this purchase, 8 to 128 characters. Reuse it verbatim on any retry.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Goes well beyond the annotations: unattended charge against a pre-enrolled card, no payment page, spend bounded by operator consent caps and maxSpendUsd, automatic full refund on undeliverable charges, and idempotency semantics including the operation_id_conflict refusal. IdempotentHint and destructiveHint are consistent with the text. Minor gap: it never states where the returned appraisal/stored charge appears versus what the status tool returns, though the output schema covers that.

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-loaded with the rail identity and price, then preconditions, then idempotency, then exclusions — a sensible progression with no filler sentences. It is dense and long for a tool description, but nearly every clause carries decision-relevant or safety-relevant information.

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

Completeness5/5

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

For a money-moving, open-world, destructive, idempotent purchase tool this covers what an agent needs: auth artifacts, cost, consent bounds, double-charge protection, async fallback, and refund guarantee. An output schema exists, so the absence of return-value details in the description is not a gap.

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 100%, so the baseline is 3, but the description adds real meaning the schema does not: that grantId and cardRef must come from the operator's prior enrollment/grant, and that operationId reuse with an identical request returns the stored charge while a different request is refused. maxSpendUsd's interaction with operator consent caps is only implied.

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?

Opens with a scoped verb+resource+price ("Buy a fresh appraisal of one domain, computed on this server, for $5") and immediately names the rails it is not — buy_appraisal (human checkout) and purchase_appraisal (prepaid balance). An agent can pick this tool over its closest siblings without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit preconditions (agent token, grantId, cardRef from operator, enrolled card) and two explicit exclusions with the alternative tool named for each. Failure/retry routing is also spelled out: poll appraisal_card_order_status with the same operationId if delivery is not immediate.

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