Skip to main content
Glama
Sign In
Alephant MCP

Alephant MCP

Official
by AlephantAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_usage_summary

Read-onlyIdempotent

Retrieve total spend, request count, and token usage for a chosen time period, such as 24 hours or a billing cycle.

Instructions

Returns total spend, requests, and token usage for the selected period.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_usage_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
periodNoAggregation windowbilling_cycle

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and idempotentHint, so the description's basic statement is consistent but does not add additional behavioral context such as caching or permissions.

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 sentence that efficiently conveys core functionality without extraneous information, front-loaded with the key action.

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?

For a simple read-only tool with one parameter and full annotation coverage, the description provides essential information about what is returned and the period parameter. It could mention aggregation scope, but it is functional.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with a description and enum for the 'period' parameter. The description does not elaborate on parameter semantics, but the schema already provides sufficient information.

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 total spend, requests, and token usage for a selected period, using a specific verb and resource. This distinguishes it from siblings like get_cost_by_model or get_daily_costs.

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 its siblings or alternatives. The description lacks context about use cases or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools