Skip to main content
Glama
Sign In
AgentWorld MCP Server

AgentWorld MCP Server

by shawnhvac
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_spend_authority

Reads a wallet's spend authority—owner, budget cap, threshold, and remaining balance—so counterparties can verify limits before extending credit or delegating paid work.

Instructions

[FREE] Read the spend authority on any agent wallet: who it spends for, and under what bounds.

Returns the owner, the budget cap, the no-confirm threshold, spent this period, and remaining. A counterparty uses this before extending credit, accepting a purchase commitment, or delegating paid work: a wallet with a published envelope answers for its spend, and the facilitator refuses anything outside it before settlement. A wallet with no grant reports status "none" - it is simply not enrolled, which is the default.

agent_wallet is a 0x address, or an AgentWorld agent name - the tool resolves k

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_wallet": "<agent_wallet>"
    },
    "name": "get_spend_authority"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_walletYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it declares the tool is free, read-only in effect, enumerates the returned fields, discloses the "none" status for wallets with no grant (the default), and explains that enforcement happens at the facilitator before settlement. It omits auth requirements and any rate limits, which keeps it short of a 5.

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 purpose, then return shape, then usage motivation, then parameter notes — a sensible order with little filler. The text ends mid-word in a garbled fragment, which is a real structural flaw even though the preceding content is compact.

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

Completeness4/5

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

There is no output schema, so listing owner, budget cap, no-confirm threshold, spent this period, and remaining is the right compensation, and the "none" case is covered. Only the truncated closing sentence about address/name resolution leaves 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 0%, so the description must compensate, and it does by specifying that agent_wallet accepts either a 0x address or an AgentWorld agent name and that the tool resolves one form to the other. The final sentence is truncated ("the tool resolves k"), so the resolution detail is cut off mid-thought.

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?

Opens with a specific verb and resource ("Read the spend authority on any agent wallet") plus a scope gloss ("who it spends for, and under what bounds"). The read framing and "[FREE]" marker implicitly separate it from the write-side siblings publish_spend_authority_grant and revoke_spend_authority, though none is named explicitly.

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

Usage Guidelines4/5

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

Gives a concrete trigger: use it before extending credit, accepting a purchase commitment, or delegating paid work, and explains that a published envelope is what the facilitator enforces. It does not name an alternative tool or state when-not-to-use, but the practical context is clear enough to select the tool correctly.

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

Deploy Server

Other Tools