Skip to main content
Glama
ActaLumen

@actalumen/mcp-server

Official
by ActaLumen

get_usage

Check your organization's plan and remaining allowance for documents, verifications, chat messages, and generated media before starting expensive batch operations.

Instructions

Check the organization's current plan, quota, and remaining allowance for documents, verifications, chat messages, and generated media. Call before kicking off expensive batch operations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main tool definition for 'get_usage'. Uses defineTool to create a tool that calls GET /v1/usage via the client to check the organization's current plan, quota, and remaining allowance.
    import { z } from "zod";
    import { defineTool } from "./types.js";
    
    const Input = z.object({}).describe("No arguments.");
    
    export const getUsage = defineTool({
      name: "get_usage",
      description:
        "Check the organization's current plan, quota, and remaining allowance for documents, verifications, chat messages, and generated media. Call before kicking off expensive batch operations.",
      inputSchema: Input,
      handler: async (_input, { client }) => client.get("/v1/usage"),
    });
  • Input schema: an empty Zod object (no arguments required) with description 'No arguments.'
    const Input = z.object({}).describe("No arguments.");
  • src/tools/index.ts:9-9 (registration)
    Import of the getUsage tool from its module.
    import { getUsage } from "./get_usage.js";
  • Registration of getUsage in the tools array, making it available as an MCP tool.
    getUsage,
  • The defineTool helper function used to define the get_usage tool with proper typing.
    export function defineTool<Input extends z.ZodTypeAny>(t: {
      name: string;
      description: string;
      inputSchema: Input;
      handler: (input: z.infer<Input>, ctx: ToolContext) => Promise<unknown>;
    }): ToolDef {
      return t as unknown as ToolDef;
    }
Behavior4/5

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

Indicates a read-only check operation (no mutations implied), but could add more detail like response format or data freshness. Still adequate given no annotations.

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 with no wasted words, front-loading key information about what is checked and when to use.

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 parameterless tool, description fully covers purpose, resources checked, and usage guidance. No output schema needed for this simple status check.

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?

No parameters; schema coverage is 100%, and description adds no param info needed. Baseline 4 for zero parameters.

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 clearly specifies the tool checks the organization's current plan, quota, and remaining allowance for documents, verifications, chat messages, and generated media, distinguishing it from sibling tools that operate on individual items.

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

Usage Guidelines5/5

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

Explicitly advises to call before expensive batch operations, providing a clear use case and context for when to invoke this tool.

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/ActaLumen/mcp-server'

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