Skip to main content
Glama
Sign In
Code-Fundi MCP Server

Code-Fundi MCP Server

Official
by Code-Fundi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

code-fundi-usage-stats

Read-only

Get query-type usage statistics for a selected date range. Review counts, credit costs, and average durations to monitor API consumption.

Instructions

Get query-type usage statistics for a given date range. Shows breakdown by query type with counts, credit costs, and average durations.

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": "code-fundi-usage-stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
rangeNoTime range per OpenAPI (default: 7d)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

A4.3/5.0
Behavior4/5

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

readOnlyHint=true already signals a safe read operation. The description adds what output to expect (breakdown by query type with counts, credit costs, average durations), giving useful behavioral context beyond the annotation.

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?

Two concise sentences, front-loaded with the primary action and followed by a clear summary of the returned breakdown. No wasted words.

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 simple read-only stats tool with one optional parameter and no output schema, the description adequately explains what the tool returns and its scope. The schema handles the parameter details.

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%, with the single parameter 'range' fully documented (enum values, default). The description mentions 'date range' but adds no new meaning beyond the schema, so baseline 3 applies.

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?

Description uses specific verb 'Get' with resource 'query-type usage statistics', clearly scoped to a date range. It lists the breakdown dimensions (counts, credit costs, average durations), which distinguishes it from sibling tools like activity stats.

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?

States clear context: for a given date range. Does not explicitly mention when not to use it or name alternatives, but the specificity of 'query-type usage statistics' implies its purpose relative to siblings.

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