Skip to main content
Glama
StripFeed

stripfeed-mcp-server

Official

check_usage

Monitor your monthly API usage and plan limits to manage resources effectively.

Instructions

Check your current monthly API usage and plan limits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The 'check_usage' tool is registered and implemented directly using server.tool, calling the /usage endpoint of the StripFeed API.
    server.tool(
      "check_usage",
      "Check your current monthly API usage and plan limits.",
      {},
      async () => {
        const apiKey = getApiKey();
        const response = await fetch(`${BASE_URL}/usage`, {
          headers: { Authorization: `Bearer ${apiKey}` },
        });
    
        if (!response.ok) {
          const body = await response.text();
          let message: string;
          try {
            message = JSON.parse(body).error;
          } catch {
            message = body;
          }
          throw new Error(`StripFeed API error ${response.status}: ${message}`);
        }
    
        const data = await response.json();
        const lines = [
          `Plan: ${data.plan}`,
          `Usage: ${data.usage.toLocaleString()}${data.limit ? ` / ${data.limit.toLocaleString()}` : ' (unlimited)'}`,
        ];
        if (data.remaining !== null) lines.push(`Remaining: ${data.remaining.toLocaleString()}`);
        lines.push(`Resets: ${data.resetsAt}`);
    
        return {
          content: [{ type: "text" as const, text: lines.join("\n") }],
        };
      }
    );
Behavior2/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It mentions the 'monthly' time scope but fails to disclose whether this is a read-only operation, what data format is returned, authentication requirements, or whether the check itself consumes API 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 7 words in a single sentence. Front-loaded with the action verb 'Check' and wastes no words. Every element contributes necessary information about the operation and its scope.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Adequate but minimal for a parameterless tool. While it identifies what is being retrieved, it lacks any indication of the return structure or format given the absence of an output schema. For a simple usage query tool, this is minimally sufficient but leaves gaps in understanding the actual output.

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?

The tool accepts zero parameters (empty properties object). According to calibration rules, 0 parameters warrants a baseline score of 4 since there are no parameter semantic gaps to fill.

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 uses the verb 'Check' and specifies the resource as 'monthly API usage and plan limits', making the scope clear. However, it does not explicitly differentiate from sibling tools (batch_fetch, fetch_url), though the resource domain is distinct enough to infer separation.

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 guidance provided on when to use this tool versus alternatives, nor any mention of prerequisites or conditions. The description states only what the tool does, not when to invoke 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/StripFeed/stripfeed-mcp-server'

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