Skip to main content
Glama
Fund-z

FundzWatch MCP Server

by Fund-z
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

get_usage

Check your API usage details including calls made, limits, and current subscription tier for monitoring your account activity.

Instructions

Check your FundzWatch API usage: calls made, limits, current tier.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:312-321 (handler)
    The handler logic for the "get_usage" tool, which fetches API usage data via a GET request and formats the response.
    case "get_usage": {
  const data = await apiRequest("GET", "/usage");
  const text =
    `FundzWatch Usage (${data.current_period}):\n\n` +
    `Tier: ${data.tier}\n` +
    `API Calls: ${data.api_calls_used} / ${data.limits.api_calls_monthly}\n` +
    `AI Score Calls: ${data.ai_score_calls_used} / ${data.limits.ai_score_calls_monthly}\n` +
    (data.last_api_call ? `Last API Call: ${data.last_api_call}` : "");
  return textResult(text);
}
  • src/index.ts:163-166 (registration)
    Registration of the "get_usage" tool in the list of available tools.
      name: "get_usage",
  description: "Check your FundzWatch API usage: calls made, limits, current tier.",
  inputSchema: { type: "object" as const, properties: {} },
},

Tool Definition Quality

A3.8/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses return values (calls made, limits, current tier) compensating for the missing output schema, but omits caching behavior, rate limit implications, or whether this request counts against quota.

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?

Extremely concise at 11 words. Front-loaded with the action verb, uses a colon to efficiently separate the operation from return value details, with zero redundant content.

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 read tool, the description adequately compensates for missing output schema by enumerating the three data fields returned. Could be improved by noting if authentication is required or caching behavior.

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?

Baseline 4 applies per rules (0 parameters). The description appropriately makes no mention of parameters since none exist, and the empty schema requires no additional semantic clarification.

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?

The description uses a specific verb ('Check') and resource ('FundzWatch API usage') and explicitly distinguishes from siblings by targeting account metadata (calls, limits, tier) rather than business data like events or leads.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit when-to-use guidance or alternatives are mentioned. While the scope is clear from context, there is no guidance on when to prefer this over other tools or prerequisites for calling it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Fund-z/fundzwatch-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server