Skip to main content
Glama
SwapHunt crypto market context

SwapHunt crypto market context

Official

get_spending

Check how much the current session has spent and how much budget remains, including payments status, USDC spent, paid calls, and the spend cap.

Instructions

Free, runs locally (no API call, no payment). Use when the user asks how much this session has spent or what budget is left. Returns whether payments are enabled, USDC spent, paid calls, the MAX_SPEND_USD cap and the remaining budget. Ex: no parameters

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses that the call is free, runs locally, makes no API call and requires no payment — behaviorally critical context for a budget tool. It stops short of explicitly declaring the operation read-only or stating whether it can fail, but the 'Returns whether...' framing makes its non-mutating nature clear.

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 cost/safety note is front-loaded, followed by the usage trigger and the return fields, so the most important information comes first. The 'Ex: no parameters' line is slightly awkward in phrasing but earns its place by stating the calling shape.

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

Completeness5/5

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

For a zero-parameter tool with no output schema, the description fully compensates by enumerating every returned field inline. Nothing an agent needs in order to decide to call it or to interpret the result is missing.

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?

There are zero parameters, which sets the baseline at 4. The description confirms this with 'Ex: no parameters,' leaving nothing to misinterpret about invocation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb+resource framing: it reports how much the current session has spent and what budget remains, then enumerates the exact return fields (payments enabled, USDC spent, paid calls, MAX_SPEND_USD cap, remaining budget). This is clearly distinguishable from the sibling market-data tools (get_price, get_fear_greed, pm_fees, etc.), which deal with market state rather than this session's own spending.

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?

It gives an explicit trigger: 'Use when the user asks how much this session has spent or what budget is left.' That is a clear when-to-use condition with no ambiguous alternatives in this tool's domain, though it does not state any when-not-to-use cases.

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