AlpineLead OI

Agent Buyer: configure hard spend limits

agent_buyer_wallet_configure

Idempotent

Set Buyer Wallet limits. No purchase is made by this tool.

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": "agent_buyer_wallet_configure"
  }
}

Input Schema

Name	Required	Description
`enabled`	No	Explicitly enable or disable autonomous purchases. Enabling requires an authorized payment method.
`daily_limit_usd`	No	Hard cumulative USD spend limit per UTC day.
`per_tx_limit_usd`	No	Hard maximum USD spend per autonomous purchase.
`monthly_limit_usd`	No	Hard cumulative USD spend limit per UTC month.
`confirm_real_money_autonomy`	No	Must be true when transitioning the wallet from disabled to enabled. This explicitly acknowledges that future agent_purchase_task calls can move real money within the configured caps.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 8, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare idempotentHint=true, destructiveHint=false, and readOnlyHint=false. The description adds the key clarification that no purchase is made, which is useful context for a configuration tool. However, it does not disclose other behavioral aspects like prerequisite conditions or side effects, so the addition is modest.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise, two short sentences with zero waste. The main purpose is front-loaded and the clarifying note about no purchase is immediately useful. Perfect structure for a simple configuration tool.

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?

Given the output schema exists and annotations cover idempotency and destructiveness, the description is adequate but not complete. It fails to mention prerequisites like the authorized payment method required for enabling (though in param description) and provides no guidance on success/failure behavior. For a configuration tool with optional params, it's minimally complete.

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 100%, so each parameter is well-documented in the schema itself. The description does not add any parameter-specific meaning beyond the generic 'Set Buyer Wallet limits', which adds no new value over the schema. Baseline 3 is appropriate.

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 clear verb ('Set') and resource ('Buyer Wallet limits'), and explicitly says 'No purchase is made by this tool', which distinguishes it from purchase actions. However, it does not differentiate from the sibling agent_buyer_wallet_setup, so the purpose is clear but sibling differentiation is missing.

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

Usage Guidelines2/5

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

The description gives no explicit guidance on when to use this tool versus alternatives like agent_buyer_wallet_setup or agent_buyer_wallet_status. The only hint is 'No purchase is made', which implies it's not for purchasing, but there is no clear when-to-use/when-not-to-use context.

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

All AlpineLead OI 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?