Skip to main content
Glama
Sign In
Courtship

Courtship

by grimmdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

report_usage

Returns the current session token ledger and savings breakdown so you can review usage and cost savings at a glance.

Instructions

Returns the current session token ledger and savings breakdown.

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": "report_usage"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It doesn't state that the call is side-effect free, whether reading the ledger consumes or resets anything, whether the numbers are per-session only, or whether the results are cached. "Current session" is the only real behavioral signal provided.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence with no filler and the key noun phrases front-loaded. It earns its place but is minimal to the point of being thin, with no structural cues such as what the breakdown contains.

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?

With no output schema and no annotations, the description is the only source of return-value information, and it names the two returned artifacts (ledger and savings breakdown) without indicating their shape, units, or granularity. For a simple zero-parameter tool that is minimally adequate but not complete.

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 takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description correctly makes no attempt to describe inputs.

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 pairs a specific verb ("Returns") with two named resources ("current session token ledger" and "savings breakdown"), so an agent can tell this is a read-only usage report. It does not differentiate from siblings, but the siblings listed (discover_tools, load_tool_schema, call_tool, love_task) are not plausible alternatives, so the lack of explicit differentiation is a minor gap.

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?

There is no explicit when-to-use guidance, no prerequisites, and no mention of alternatives. The phrase "current session" implies the scope of use but leaves the agent to infer when reporting is warranted versus simply continuing other work.

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