Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

account_get_api_usage

Retrieve recent API request history, optionally filtering by endpoint, HTTP status code, or page, to review usage and troubleshoot requests.

Instructions

account: Get request history. GET /v1/account/get-api-usage. Call it with no arguments for the recent page. endpoint, statusCode and page are optional filters. View your recent API request history 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_api_usage"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number for pagination (max 100)
endpointNoFilter by endpoint name (partial match)
statusCodeNoFilter by HTTP status code

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/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 the credit cost on success and enumerates which outcomes are free (errors, blocked/timed-out, invalid requests, cache hits) plus the conditional charge for empty/not-found results. It stops short of describing ordering, page size, or what a result record contains.

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 and endpoint are front-loaded, and the parameter note comes before the billing rules, which is the right order. The cost section is slightly dense and could be split for readability, but no sentence is pure filler.

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 three-optional-parameter read tool with no output schema and no annotations, the definition covers purpose, defaults, filters, and the credit model, which is enough to call it correctly. The remaining gap is that the shape of the returned request-history records is never characterized.

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?

Schema coverage is 100%, so the baseline is 3, and the description mostly restates that endpoint, statusCode and page are optional filters. The one genuine addition is the default behavior — calling with no arguments returns the recent page — which the schema alone does not state; the partial-match detail for endpoint stays only in the schema.

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 opens with a specific verb and resource ("Get request history") and pins it to the concrete endpoint GET /v1/account/get-api-usage. It is clearly distinguishable from usage-summary siblings like account_get_daily_usage_count or account_get_most_used_routes by being a per-request log, though it never names those siblings explicitly.

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 tells the agent to call with no arguments for the recent page and that the three fields are optional filters, which implies the common usage. However, there is no explicit guidance on when to prefer this over the daily-count or most-used-routes siblings, and no stated exclusions or prerequisites.

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