Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

account_get_most_used_routes

Identify which API endpoints you use frequently, with optional ISO-8601 start and end times to review usage over a chosen period.

Instructions

account: Get most used routes. GET /v1/account/get-most-used-routes. Call it with no arguments for the default window. start_time and end_time are optional ISO-8601 bounds. See which endpoints you use the most 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_most_used_routes"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_timeNoEnd of time range (ISO 8601 format)
start_timeNoStart of time range (ISO 8601 format)

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, the description carries the full burden and does disclose a real behavioral trait: a detailed credit-cost model (1 credit on success; errors, blocked/timeout, invalid requests and cache hits free; empty results charged per published cost). It omits return shape and pagination/result-size behavior, so it is strong but not complete.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and endpoint are front-loaded and the argument guidance follows sensibly. The trailing cost paragraph is long, generic billing boilerplate (three sentences on what is and isn't charged) that crowds out more useful content such as what the response contains.

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?

A read-only, two-optional-param analytics call with no output schema and no annotations; the description covers scope, argument defaults, and the cost side effect, which is what an agent needs to call it safely. Only the shape of the returned route ranking is unexplained, a minor gap for a simple read.

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?

Schema coverage is 100% and the schema already documents both ISO-8601 params, so baseline is 3. The description adds meaning beyond the schema by stating that both are optional and that omitting them selects a default window, which an agent cannot infer from the schema alone.

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?

States a specific verb and resource ('Get most used routes') and disambiguates the vague word 'routes' with 'See which endpoints you use the most.' It is clearly distinct from account_get_api_usage and account_get_daily_usage_count in intent, though it does not name them.

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?

Gives concrete invocation guidance ('Call it with no arguments for the default window') and marks start_time/end_time as optional, which tells an agent how to call it. It never says when to prefer this over the related usage/credit siblings, so the choice among account analytics tools is left implicit.

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