Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

account_get_daily_usage_count

Retrieve daily credit and request counts to track usage trends and monitor account consumption day by day.

Instructions

account: Get daily usage. GET /v1/account/get-daily-usage-count. Call it with no arguments. Each row is one day. Get your daily credit and request counts 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_get_daily_usage_count"
  }
}

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, the description carries the full burden and does substantial work: it discloses the credit cost on success, that errors/blocked/timed-out/invalid requests and cache hits are free, and how not-found or empty results are billed. That is unusually rich billing context. It omits auth requirements, day-boundary/timezone semantics, and how far back history goes.

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?

Purpose is front-loaded, and the endpoint path and argument guidance follow immediately. There is mild redundancy between 'Get daily usage' and 'Get your daily credit and request counts', and the billing caveats run long, but each sentence still conveys actionable information.

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-argument, no-output-schema read tool, the definition covers what it returns (one row per day with credit and request counts) and the cost model, which is what an agent needs to decide and invoke. The missing pieces are secondary but real: timezone/day alignment, the span of history returned, and any authentication assumptions.

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?

Zero parameters, which is the baseline-4 case, and the description confirms this explicitly with 'Call it with no arguments' so an agent will not hunt for optional filters. No further parameter meaning is needed.

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?

The description names a specific verb and resource ('Get daily usage') and clarifies the payload ('daily credit and request counts', 'Each row is one day'), which distinguishes it from aggregate siblings like account_get_api_usage. It stops short of explicitly contrasting itself with account_credit_balance or account_get_most_used_routes, so it is clear but not sibling-differentiating.

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?

It states the invocation shape ('Call it with no arguments'), which is useful, but gives no when-to-use context relative to the other account_* tools and no exclusions. The per-day granularity implies the use case rather than stating it.

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