Skip to main content
Glama

venice_get_rate_limit_logs

Retrieve historical rate limit usage logs to monitor API consumption and manage quotas effectively.

Instructions

Get rate limit usage history logs

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function that executes the tool logic: fetches rate limit logs from the Venice API and returns formatted JSON or error.
    async () => {
      const response = await veniceAPI("/api_keys/rate_limits/logs");
      const data = await response.json() as { data?: unknown; error?: { message?: string } };
      if (!response.ok) return { content: [{ type: "text" as const, text: `Error: ${data.error?.message || response.statusText}` }] };
      return { content: [{ type: "text" as const, text: JSON.stringify(data.data, null, 2) }] };
    }
  • Registers the venice_get_rate_limit_logs tool with the MCP server, using an empty input schema and the inline handler.
    server.tool(
      "venice_get_rate_limit_logs",
      "Get rate limit usage history logs",
      {},
      async () => {
        const response = await veniceAPI("/api_keys/rate_limits/logs");
        const data = await response.json() as { data?: unknown; error?: { message?: string } };
        if (!response.ok) return { content: [{ type: "text" as const, text: `Error: ${data.error?.message || response.statusText}` }] };
        return { content: [{ type: "text" as const, text: JSON.stringify(data.data, null, 2) }] };
      }
    );
  • src/index.ts:18-18 (registration)
    Top-level call to registerAdminTools, which registers the admin tools including venice_get_rate_limit_logs.
    registerAdminTools(server);
Behavior2/5

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

With no annotations, the description carries full burden but only states what the tool does, not how it behaves. It lacks details on permissions needed, rate limits of the tool itself, response format, pagination, or data retention policies. This is inadequate for a tool that likely returns sensitive usage data.

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 is a single, efficient sentence with no wasted words. It's front-loaded with the core purpose, making it easy for an agent to parse quickly. Every word earns its place.

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 no annotations and no output schema, the description is incomplete. It doesn't explain what 'history logs' include (e.g., time range, format, granularity) or behavioral aspects like authentication needs. For a tool that likely returns structured historical data, this leaves significant gaps.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter info, which is fine here. Baseline is 4 for zero parameters, as it avoids unnecessary complexity.

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 rate limit usage history logs' clearly states the action (get) and resource (rate limit usage history logs). It distinguishes from sibling 'venice_get_rate_limits' by specifying 'history logs' rather than current limits. However, it doesn't explicitly contrast with that sibling, keeping it at 4 rather than 5.

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 is provided on when to use this tool versus alternatives like 'venice_get_rate_limits'. The description implies usage for historical data but doesn't specify scenarios, prerequisites, or exclusions, leaving the agent with minimal context.

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/georgeglarson/venice-mcp'

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