BARMAN by CeoAgentAI

prepare_microtask

Idempotent

Prepare one tiny service; no payment is initiated.

        JSON/schema check: 0.01 USDC. Public HTTPS evidence for 1-5 URLs:
        0.05 USDC, anonymous GET only, explicit probe permission. Optional
        support: 0.01 USDC. Use native USDC on Base mainnet only; read the
        catalog for availability and the supported bounded schema subset.
        Omit secrets. Keep the quote and receipt token private. A prepared
        quote is not a payment or permission for this agent to spend.

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": {
      "product_id": "<product_id>",
      "payer_address": "<payer_address>",
      "expected_total_usdc": "<expected_total_usdc>",
      "accept_price": "<accept_price>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "prepare_microtask"
  }
}

Input Schema

Name	Required	Description	Default
`urls`	No
`json_text`	No
`product_id`	Yes
`json_schema`	No
`accept_price`	Yes
`payer_address`	Yes
`idempotency_key`	Yes
`allow_public_probe`	No
`expected_total_usdc`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 26, 2026

TDQS

A3.6/5.0

Behavior4/5

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

The description adds substantial behavior beyond annotations: no payment is initiated, pricing is disclosed, anonymous GET only is required for URL probes, secrets should be omitted, and the quote/receipt token must remain private. These are useful operational and safety details that complement the annotations rather than contradict them.

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?

The description front-loads the core purpose and then packs pricing, network, privacy, and scope constraints into a compact block. It is dense but mostly efficient; a few phrases like 'one tiny service' are slightly vague rather than wasteful.

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 tool is complex with 9 parameters, but it has annotations and an output schema, so the description need not explain return values or full safety semantics. Still, it omits guidance for several required parameters and does not explicitly route the agent to confirm_microtask after preparing a quote.

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?

With 0% schema description coverage, the description compensates partially by explaining product pricing, the 1-5 URL evidence limit, anonymous GET probing, and a bounded schema subset. However, required parameters such as payer_address, accept_price, and idempotency_key are not explained, leaving clear semantic gaps.

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 states a specific verb-resource pair: prepare one microtask/quote for a tiny service, and explicitly says no payment is initiated. It does not name a sibling tool, but the no-payment scope meaningfully distinguishes it from confirm_microtask or place_order.

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?

It gives usage constraints such as reading the catalog first, using native USDC on Base mainnet only, and requiring explicit probe permission, but it never explicitly says when to use this tool versus confirm_microtask or place_order. The intended workflow is implied rather than stated.

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

All BARMAN by CeoAgentAI tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?