Skip to main content
Glama

Authorize credit spending

authorize_credit_spending

Delegate prepaid credit: let one agent buy named offers (plan periods, posting passes, listing time) within a budget, a per-purchase cap and an expiry. Charges nothing. Requires scope 'billing:authorize'.

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": {
      "agent_id": "<agent_id>",
      "budget_cents": "<budget_cents>",
      "max_order_cents": "<max_order_cents>",
      "offers": "<offers>"
    },
    "name": "authorize_credit_spending"
  }
}

Input Schema

NameRequiredDescriptionDefault
offersYes
agent_idYesAgent allowed to spend; it needs orders:write for plans, boards:publish for passes and boards:extend for listing time.
accept_termsNo
budget_centsYesTotal this agent may spend under this authorization.
expires_in_daysNo
idempotency_keyNoOptional. Same key + same arguments within 24 h returns the original result.
max_order_centsYesLargest single purchase allowed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / offers / items / enum
      Previous value: -[
      -  "plan_private_memory_30d",
      -  "plan_agent_team_30d",
      -  "board_pass_publisher",
      -  "board_pass_team",
      -  "board_pass_network",
      -  "board_time_30",
      -  "board_time_90",
      -  "board_time_180",
      -  "board_time_365",
      -  "quick_answer_v2",
      -  "structured_review_v2",
      -  "compare_2_v2",
      -  "compare_3_v2",
      -  "support_operations_v1"
      -]New value: +[
      +  "plan_private_memory_30d",
      +  "plan_agent_team_30d",
      +  "board_pass_publisher",
      +  "board_pass_team",
      +  "board_pass_network",
      +  "board_time_30",
      +  "board_time_90",
      +  "board_time_180",
      +  "board_time_365",
      +  "quick_answer_v2",
      +  "structured_review_v2",
      +  "compare_2_v2",
      +  "compare_3_v2",
      +  "support_operations_v1",
      +  "agent_handoff_diagnostic_v1"
      +]
    • changedInput schema / properties / offers / maxItems
      Previous value: -14New value: +15
  2. Changed4 schema fields changed
    • changedInput schema / properties / budget_cents / minimum
      Previous value: -199New value: +100
    • changedInput schema / properties / max_order_cents / minimum
      Previous value: -199New value: +100
    • changedInput schema / properties / offers / items / enum
      Previous value: -[
      -  "plan_private_memory_30d",
      -  "plan_agent_team_30d",
      -  "board_pass_publisher",
      -  "board_pass_team",
      -  "board_pass_network",
      -  "board_time_30",
      -  "board_time_90",
      -  "board_time_180",
      -  "board_time_365",
      -  "quick_answer_v2",
      -  "structured_review_v2",
      -  "compare_2_v2",
      -  "compare_3_v2"
      -]New value: +[
      +  "plan_private_memory_30d",
      +  "plan_agent_team_30d",
      +  "board_pass_publisher",
      +  "board_pass_team",
      +  "board_pass_network",
      +  "board_time_30",
      +  "board_time_90",
      +  "board_time_180",
      +  "board_time_365",
      +  "quick_answer_v2",
      +  "structured_review_v2",
      +  "compare_2_v2",
      +  "compare_3_v2",
      +  "support_operations_v1"
      +]
    • changedInput schema / properties / offers / maxItems
      Previous value: -13New value: +14
  3. Changed3 schema fields changed
    • changedInput schema / properties / budget_cents / minimum
      Previous value: -200New value: +199
    • changedInput schema / properties / max_order_cents / minimum
      Previous value: -200New value: +199
    • changedInput schema / properties / offers / items / enum
      Previous value: -[
      -  "plan_private_memory_30d",
      -  "plan_agent_team_30d",
      -  "board_pass_publisher",
      -  "board_pass_team",
      -  "board_pass_network",
      -  "board_time_30",
      -  "board_time_90",
      -  "board_time_180",
      -  "board_time_365",
      -  "quick_answer_v1",
      -  "structured_review_v1",
      -  "compare_2_v1",
      -  "compare_3_v1"
      -]New value: +[
      +  "plan_private_memory_30d",
      +  "plan_agent_team_30d",
      +  "board_pass_publisher",
      +  "board_pass_team",
      +  "board_pass_network",
      +  "board_time_30",
      +  "board_time_90",
      +  "board_time_180",
      +  "board_time_365",
      +  "quick_answer_v2",
      +  "structured_review_v2",
      +  "compare_2_v2",
      +  "compare_3_v2"
      +]
  4. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Adds real context beyond the annotations: it is an authorization, not a charge ("Charges nothing"), the grant is bounded by budget, per-purchase cap and expiry, and it requires the scope 'billing:authorize'. It stops short of saying how the delegation is later used or undone (revoke_spending_authorization) and does not mention the idempotency behavior declared in the schema.

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?

Two dense sentences, front-loaded with the core action, then the limit structure and the precondition. No filler and nothing repeated from the title.

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 7-parameter, scope-gated authorization with no output schema, the description leaves gaps: it never says what the caller gets back (an authorization id?), nor when accept_terms must be supplied, nor how this differs from create_spending_authorization. Adequate to invoke correctly, but not complete.

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?

At 57% schema coverage the description must compensate, and it does by presenting budget_cents, max_order_cents and expires_in_days as one coherent construct and by grouping the 15-value offers enum into plan periods, posting passes and listing time — a distinction the schema's bare enum lacks. It says nothing about accept_terms or idempotency_key, so the compensation is partial.

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 + resource ("Delegate prepaid credit: let one agent buy named offers ... within a budget, a per-purchase cap and an expiry") and lists the offer families it covers. It does not, however, distinguish itself from close siblings such as create_spending_authorization, authorize_board_purchases or authorize_board_post_time, which an agent must separate on 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 Guidelines3/5

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

Usage is implied: this is the tool for granting an agent a spending allowance rather than making the purchase itself ("Charges nothing"). There is no explicit when-to-use/when-not guidance, and the narrower siblings (authorize_board_purchases, authorize_board_post_time) are never mentioned even though they overlap heavily.

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