Skip to main content
Glama

manage_buyer_finops_spend_passport

[Private by default] Protect your budget: set per-payment and daily USDC limits for your agent and compare LLM costs. Free signup includes 1 unlock. Example: buyerId='alphaquant-agent'.

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

Input Schema

NameRequiredDescriptionDefault
buyerIdNoUnique buyer agent identifier.
buyerNameNoHuman-readable name of the buyer agent.
walletAddressNoBuyer wallet address.
dailySpendCapUsdcNoMaximum authorized daily spend cap in USDC.
maxSpendPerTxUsdcNoMaximum authorized spend per transaction in USDC.
activeRfqDescriptionNoBrief procurement requirement description for 2★/3★ sellers.
proposedPurchaseUsdcNoOptional purchase amount to test against FinOps caps and VIP discounts.
estimatedPromptTokensNoToken count to benchmark LLM inference cost across providers.
lookingToBuyVerticalsNoVerticals this buyer is actively purchasing.
listMeInBuyerDirectoryNoOptional, default private. true = 2-3 star sellers can see your budget and interests and send offers; false = remove yourself.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / listMeInBuyerDirectory
      Added value: +{
      +  "description": "Optional, default private. true = 2-3 star sellers can see your budget and interests and send offers; false = remove yourself.",
      +  "type": "boolean"
      +}
  2. Changed10 schema fields changed
    • changedInput schema / properties / activeRfqDescription / description
      Previous value: -"Short description of what the buyer agent wants to purchase or audit."New value: +"Brief procurement requirement description for 2★/3★ sellers."
    • addedInput schema / properties / buyerId / description
      Added value: +"Unique buyer agent identifier."
    • addedInput schema / properties / buyerId / examples
      Added value: +[
      +  "alphaquant-agent"
      +]
    • addedInput schema / properties / buyerName / description
      Added value: +"Human-readable name of the buyer agent."
    • addedInput schema / properties / dailySpendCapUsdc / description
      Added value: +"Maximum authorized daily spend cap in USDC."
    • changedInput schema / properties / estimatedPromptTokens / description
      Previous value: -"Optional token count to benchmark LLM inference cost savings."New value: +"Token count to benchmark LLM inference cost across providers."
    • changedInput schema / properties / lookingToBuyVerticals / description
      Previous value: -"Verticals this buyer agent is looking to purchase (e.g. ['VERTICAL_3_SOLIDITY_SECURITY', 'VERTICAL_5_CERTIFIED_SKILLS'])."New value: +"Verticals this buyer is actively purchasing."
    • addedInput schema / properties / maxSpendPerTxUsdc / description
      Added value: +"Maximum authorized spend per transaction in USDC."
    • changedInput schema / properties / proposedPurchaseUsdc / description
      Previous value: -"Optional purchase amount in USDC to test against spend caps and apply VIP buyer discounts."New value: +"Optional purchase amount to test against FinOps caps and VIP discounts."
    • addedInput schema / properties / walletAddress / description
      Added value: +"Buyer wallet address."
  3. Changed2 schema fields changed
    • addedInput schema / properties / activeRfqDescription
      Added value: +{
      +  "description": "Short description of what the buyer agent wants to purchase or audit.",
      +  "type": "string"
      +}
    • addedInput schema / properties / lookingToBuyVerticals
      Added value: +{
      +  "description": "Verticals this buyer agent is looking to purchase (e.g. ['VERTICAL_3_SOLIDITY_SECURITY', 'VERTICAL_5_CERTIFIED_SKILLS']).",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  4. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already indicate a non-read-only, non-destructive, non-idempotent write operation. The description adds the default privacy setting and the free unlock limit, but doesn't explain permissions, reversibility, or the effect of repeated calls, leaving some behavioral gaps.

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

Conciseness3/5

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

The description is a single sentence with an example, but mixes privacy default, core function, and pricing in a somewhat disjointed way. It's not overly long but could be better structured for front-loading the primary action.

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?

For a tool with 10 parameters and no output schema, the description gives a basic overview but omits explaining the 'spend passport' concept, how parameters interact, or what the tool returns. Annotations cover some safety aspects, but the description could be more thorough.

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 100% schema coverage, the schema already documents all 10 parameters. The description provides an example for buyerId and implicitly links to maxSpendPerTxUsdc and dailySpendCapUsdc, but adds little meaning beyond the schema for other parameters.

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 clearly states the tool sets per-payment and daily USDC limits and compares LLM costs, using specific verbs and resources. It distinguishes itself from sibling audit/escrow tools by focusing on FinOps budget management, though it doesn't name a specific alternative.

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?

The description implies usage for protecting a budget and setting spending caps but offers no explicit when-to-use or when-not-to-use guidance, nor does it reference alternatives. The mention of free signup with one unlock is informative but not about tool selection.

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.