Skip to main content
Glama
Sign In
dex-data

dex-data

by donnywin85
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_spend_budget

Check the amount spent on paid calls in the current session and view the applicable spending caps.

Instructions

How much this session has spent on paid calls, and the caps in force. Free, local, and makes the cost of continuing visible before it is incurred.

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_spend_budget"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

The description openly states that the tool is free and local, indicating no side effects or network calls. It does not mention rate limits or other constraints, but given its read-only nature, the transparency is adequate.

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 succinct, using a single sentence to convey the purpose and key attributes. Every word contributes to the meaning without unnecessary detail.

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 tool with no parameters and no output schema, the description fully covers its purpose, cost implications, and local execution. It provides sufficient context for an agent to decide when and how to invoke it.

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?

The tool has no parameters and the schema is fully covered (100%), so the description adds no parameter-specific information. The baseline of 3 applies as there is nothing to clarify.

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 clearly states that the tool reports the amount spent on paid calls and the active caps. It is specific and immediately understandable, leaving no ambiguity about its function.

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?

The description implies when to use it (to check budget before incurring more costs) and notes it is free and local, but does not explicitly contrast with sibling tools or state a precise trigger condition. Still, the context is inferable.

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