Skip to main content
Glama

get_costs

Retrieve current month cost breakdown: total spend, cost by model, and estimated savings from guard interventions.

Instructions

Get cost breakdown for the current month: total spend, cost by model, and estimated savings from guard interventions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The 'get_costs' tool definition with its handler. The handler calls client.getCosts() and returns the JSON-serialized result.
    {
      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);
      },
    },
  • The getCosts() method on AgentGuardClient that calls the REST API endpoint /api/v1/costs and returns typed cost data including monthly totals, per-model costs, and guard savings.
    async getCosts() {
      return this.fetch<{
        monthly: { total_cost: number; trace_count: number };
        by_model: Array<{ model: string; total_cost: number; call_count: number }>;
        savings: { guard_events: number; estimated_savings: number };
      }>("/api/v1/costs");
    }
  • The 'get_costs' tool is registered as part of the 'tools' array exported from tools.ts, alongside other tools like query_traces, get_trace, etc.
    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,
          );
        },
      },
    ];
  • The ToolDefinition interface that defines the schema shape including name, description, inputSchema (with properties and required fields), and the handler function signature.
    export interface ToolDefinition {
      name: string;
      description: string;
      inputSchema: {
        type: "object";
        properties: Record<string, unknown>;
        required?: string[];
      };
      handler: (client: AgentGuardClient, args: Record<string, unknown>) => Promise<string>;
    }
Behavior3/5

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

With no annotations, the description bears full responsibility for behavioral disclosure. It adds context about the scope (current month) and output structure but does not mention whether costs are real-time, if it is read-only, or any potential limits. It is adequate but not thorough.

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, concise sentence that front-loads the core purpose. Every word adds value, with no redundancy or unnecessary detail.

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?

Given no output schema or annotations, the description provides a reasonable overview of the tool's output but lacks details on the exact format, time granularity, or data freshness. It is minimally complete for a simple cost retrieval tool but could be more informative.

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 zero parameters, so the schema coverage is 100%. Following the instruction, a baseline of 4 is appropriate since no parameter description is needed and the description does not add parameter information beyond what is obvious.

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 returns a cost breakdown for the current month, listing specific outputs (total spend, cost by model, estimated savings). It distinguishes well from sibling tools like check_budget or get_usage.

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?

The description implies usage for retrieving a monthly cost summary but does not explicitly state when to use this tool versus alternatives such as check_budget or get_alerts. No exclusions or guidance are provided.

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