Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

account_credit_balance

Retrieve your remaining Fetchproof API credit balance before making billed requests.

Instructions

account: Get credit balance. GET /v1/account/credit-balance. Call it with no arguments. Get your remaining credit balance. Costs 1 credit when it succeeds. Errors, blocked or timed-out requests, invalid requests and cache hits cost nothing. A not-found or empty result is charged only where that operation's published cost says so.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and does substantial work: it discloses that a successful call costs 1 credit, and that errors, blocked, timed-out, invalid requests and cache hits are free. That is exactly the kind of billing/behavioral detail an agent cannot get from structured fields. It stops short of stating authentication requirements or failure modes.

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 name, verb and endpoint, and every sentence is short and scannable. There is mild redundancy between "Get credit balance" and "Get your remaining credit balance," and the final clause about not-found results is somewhat convoluted, but nothing is wasted.

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?

For a zero-parameter, annotation-free tool with no output schema, the description covers the essentials: what it returns, that it takes no arguments, and the exact cost model. The only real gap is that the absence of an output schema means a sentence on the response shape (e.g. remaining credit and currency) would have helped.

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?

The schema has zero parameters, so the baseline is 4. The description reinforces this with "Call it with no arguments," leaving no ambiguity about how to invoke it.

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?

"Get credit balance" plus the concrete endpoint GET /v1/account/credit-balance states a specific verb and resource, and "remaining credit balance" makes the returned value unambiguous. It does not name a sibling, but the resource is inherently distinct from the account usage tools, so an agent can still route correctly.

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?

"Call it with no arguments" is invocation guidance rather than usage guidance. There is no statement of when to prefer this over account_get_api_usage or the daily-count sibling, so the agent must infer the split from names alone.

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