Skip to main content
Glama

get_usage

Monitor your event quota usage and plan limits to avoid exceeding your budget. Shows event count, retention period, and plan details.

Instructions

Check your current event quota usage and plan limits. Shows event count vs limit, retention period, and plan details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for the get_usage tool. Calls client.getUsage() and formats the response with a computed usage_percent field.
    handler: async (client) => {
      const result = await client.getUsage();
      const pct = result.event_limit > 0
        ? ((result.event_count / result.event_limit) * 100).toFixed(1)
        : "0";
      return JSON.stringify({ ...result, usage_percent: `${pct}%` }, null, 2);
    },
  • Input schema for get_usage — no parameters required (empty object).
    inputSchema: {
      type: "object",
      properties: {},
    },
  • Tool definition array registration. get_usage is registered as one of the tool objects in the tools array with name, description, inputSchema, and handler.
    export const tools: ToolDefinition[] = [
      {
        name: "query_traces",
        description:
          "Search recent traces from your AgentGuard-instrumented agents. " +
          "Filter by service name, time range, or paginate through results.",
        inputSchema: {
          type: "object",
          properties: {
            limit: { type: "number", description: "Max traces to return (default 20, max 500)" },
            offset: { type: "number", description: "Offset for pagination" },
            service: { type: "string", description: "Filter by service name" },
            since: { type: "string", description: "ISO timestamp — only traces after this time" },
            until: { type: "string", description: "ISO timestamp — only traces before this time" },
          },
        },
        handler: async (client, args) => {
          const result = await client.getTraces({
            limit: args.limit ? String(args.limit) : "20",
            offset: args.offset ? String(args.offset) : undefined,
            service: args.service as string | undefined,
            since: args.since as string | undefined,
            until: args.until as string | undefined,
          });
          return JSON.stringify(result, null, 2);
        },
      },
      {
        name: "get_trace",
        description:
          "Get the full event tree for a specific trace by its trace ID. " +
          "Shows all spans, tool calls, LLM calls, guard triggers, and errors.",
        inputSchema: {
          type: "object",
          properties: {
            trace_id: { type: "string", description: "The trace ID to look up" },
          },
          required: ["trace_id"],
        },
        handler: async (client, args) => {
          const result = await client.getTrace(args.trace_id as string);
          return JSON.stringify(result, null, 2);
        },
      },
      {
        name: "get_trace_decisions",
        description:
          "Extract normalized decision.* events from one trace. " +
          "Use this when a workflow includes proposal, override, approval, or binding steps.",
        inputSchema: {
          type: "object",
          properties: {
            trace_id: { type: "string", description: "The trace ID to inspect for decision events" },
          },
          required: ["trace_id"],
        },
        handler: async (client, args) => {
          const traceId = args.trace_id as string;
          const result = await client.getTrace(traceId);
          const events = Array.isArray(result.events) ? result.events : [];
          const decisions = extractDecisionEvents(events as Array<Record<string, unknown>>, {
            traceId,
          });
          return JSON.stringify({ trace_id: traceId, decisions }, null, 2);
        },
      },
      {
        name: "get_alerts",
        description:
          "Get recent guard alerts (loop detection, budget exceeded) and errors. " +
          "Useful for checking if your agents are hitting safety limits.",
        inputSchema: {
          type: "object",
          properties: {
            limit: { type: "number", description: "Max alerts to return (default 50)" },
            since: { type: "string", description: "ISO timestamp — only alerts after this time" },
          },
        },
        handler: async (client, args) => {
          const result = await client.getAlerts({
            limit: args.limit ? String(args.limit) : undefined,
            since: args.since as string | undefined,
          });
          return JSON.stringify(result, null, 2);
        },
      },
      {
        name: "get_usage",
        description:
          "Check your current event quota usage and plan limits. " +
          "Shows event count vs limit, retention period, and plan details.",
        inputSchema: {
          type: "object",
          properties: {},
        },
        handler: async (client) => {
          const result = await client.getUsage();
          const pct = result.event_limit > 0
            ? ((result.event_count / result.event_limit) * 100).toFixed(1)
            : "0";
          return JSON.stringify({ ...result, usage_percent: `${pct}%` }, null, 2);
        },
      },
      {
        name: "get_costs",
        description:
          "Get cost breakdown for the current month: total spend, cost by model, " +
          "and estimated savings from guard interventions.",
        inputSchema: {
          type: "object",
          properties: {},
        },
        handler: async (client) => {
          const result = await client.getCosts();
          return JSON.stringify(result, null, 2);
        },
      },
      {
        name: "check_budget",
        description:
          "Quick pass/fail budget health check. Combines usage quota and cost data " +
          "to give a summary of whether you're within safe operating limits.",
        inputSchema: {
          type: "object",
          properties: {},
        },
        handler: async (client) => {
          const [usage, costs] = await Promise.all([
            client.getUsage(),
            client.getCosts(),
          ]);
    
          const usagePct = usage.event_limit > 0
            ? (usage.event_count / usage.event_limit) * 100
            : 0;
    
          const status = usagePct >= 90
            ? "critical"
            : usagePct >= 75
              ? "warning"
              : "healthy";
    
          return JSON.stringify(
            {
              status,
              plan: usage.plan,
              events: {
                used: usage.event_count,
                limit: usage.event_limit,
                percent: `${usagePct.toFixed(1)}%`,
              },
              costs: {
                monthly_total: costs.monthly.total_cost,
                trace_count: costs.monthly.trace_count,
              },
              savings: costs.savings,
            },
            null,
            2,
          );
        },
      },
    ];
  • MCP server registration loop — iterates over all tools (including get_usage) and registers them with the McpServer instance via server.tool().
    for (const tool of tools) {
      const shape = buildToolShape(tool.inputSchema.properties, tool.inputSchema.required ?? []);
    
      const toolName = tool.name;
      const handler = tool.handler;
    
      server.tool(toolName, tool.description, shape, async (args) => {
        try {
          const text = await handler(client, args as Record<string, unknown>);
          return { content: [{ type: "text" as const, text }] };
        } catch (err) {
          const message = err instanceof Error ? err.message : String(err);
          return {
            content: [{ type: "text" as const, text: `Error: ${message}` }],
            isError: true,
          };
        }
      });
    }
    
    async function main() {
      const transport = new StdioServerTransport();
      await server.connect(transport);
    }
    
    main().catch((err) => {
      console.error("Fatal:", err);
      process.exit(1);
    });
  • AgentGuardClient.getUsage() — helper method that makes the HTTP GET request to /api/v1/usage and returns typed usage data (plan, event_count, event_limit, etc.).
    async getUsage() {
      return this.fetch<{
        plan: string;
        current_month: string;
        event_count: number;
        event_limit: number;
        retention_days: number;
        max_keys: number;
        max_users: number;
      }>("/api/v1/usage");
    }
Behavior3/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. It does not explicitly state that the tool is read-only or has no side effects, though it describes a query operation. This is a minor gap in transparency.

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, no fluff. The first sentence front-loads the purpose, and the second adds specifics. Every word earns its place.

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?

Given no parameters, no output schema, and a simple query purpose, the description is largely complete. It could optionally mention the return format (object), but this is not critical.

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 no parameters, and schema coverage is 100%. The description adds value by explaining what the tool shows (event count, limit, retention, plan details), which is beyond the schema's empty object definition.

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 clearly states the tool checks event quota usage and plan limits, specifying outputs like event count vs limit, retention period, and plan details. It distinguishes from siblings (e.g., check_budget for budget, get_costs for costs).

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

Usage Guidelines3/5

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

No explicit when-to-use or when-not-to-use guidance is given. The purpose implies usage for quota checking, but alternatives are not mentioned. The description relies on the agent inferring usage from 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/bmdhodl/agent47'

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