Skip to main content
Glama
QianJue-CN

Random.org MCP Server

by QianJue-CN

getUsage

Retrieve API usage statistics to monitor your random data generation quota and track consumption patterns.

Instructions

Get API usage statistics

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The MCP server handler for the 'getUsage' tool. It calls RandomOrgClient.getUsage() and returns the result formatted as JSON text content.
    private async handleGetUsage(args: any) {
      const result = await this.randomOrgClient.getUsage();
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(result, null, 2),
          },
        ],
      };
    }
  • src/server.ts:255-262 (registration)
    Registration of the 'getUsage' tool in the ListTools response, including name, description, and empty input schema.
    {
      name: 'getUsage',
      description: 'Get API usage statistics',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • TypeScript interface defining the structure of the UsageResult returned by the Random.org API 'getUsage' endpoint.
    export interface UsageResult {
      status: string;
      creationTime: string;
      bitsLeft: number;
      requestsLeft: number;
      totalBits: number;
      totalRequests: number;
    }
  • Helper method in RandomOrgClient that makes the actual API request to Random.org's 'getUsage' endpoint using makeRequest.
    async getUsage(): Promise<UsageResult> {
      return this.makeRequest<UsageResult>('getUsage', {});
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Get API usage statistics' implies a read-only operation, but it doesn't specify details like authentication requirements, rate limits, data freshness, or response format. This leaves significant gaps in understanding the tool's behavior.

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?

The description 'Get API usage statistics' is a single, clear sentence with no wasted words. It's front-loaded and efficiently communicates the core purpose without unnecessary elaboration.

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

Completeness2/5

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

Given the lack of annotations and output schema, the description is insufficient for a tool that likely returns structured usage data. It doesn't explain what statistics are included, time ranges, or format, leaving the agent with incomplete context for effective use.

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 has 0 parameters, and the schema description coverage is 100%, so there are no parameters to document. The description doesn't need to add parameter semantics, earning a high baseline score for this dimension.

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 'Get API usage statistics' clearly states the verb ('Get') and resource ('API usage statistics'), making the tool's purpose immediately understandable. However, it doesn't differentiate this tool from its siblings, which are all data generation tools, so it doesn't reach the highest score.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention context, prerequisites, or relationships to sibling tools, leaving the agent with minimal usage direction.

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/QianJue-CN/TRUERandomMCP'

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