Skip to main content
Glama

tokmeter_projects

Read-only

Shows per-project AI token usage with cost, models, active days, and date range to identify high-consumption projects and compare resource use.

Instructions

Show per-project token usage breakdown — cost, tokens, active days, models used, and date range. Use this to see which projects are consuming the most AI resources.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax projects to show (default: 20)
scopeNoTime scope: today, week (last 7d), month (calendar month), or all (default)
projectNoFilter by project name/path substring
providersNoFilter to specific providers (e.g. ['claude-code','cursor'])

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.19.4
    • addedInput schema / properties / project
      Added value: +{
      +  "description": "Filter by project name/path substring",
      +  "maxLength": 512,
      +  "type": "string"
      +}
  2. First observedv1.19.3

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful output context (what dimensions the breakdown includes) but says nothing about defaults, result ordering, truncation, or how many projects come back before the limit applies.

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?

Two sentences, front-loaded with the resource and its output fields, then the use case. Slightly redundant between 'token usage breakdown' and 'consuming the most AI resources', but no wasted preamble.

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?

No output schema exists, and the description correctly enumerates the returned fields, which is the main thing an agent needs here. For a simple read-only aggregation tool with fully documented params, only the absence of sibling routing keeps it below 5.

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 description coverage is 100%, so limit, scope, project, and providers are all documented in the schema itself. The description doesn't mention the filtering or scoping capabilities at all, so it adds nothing beyond the schema — baseline 3 applies.

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?

States a specific verb+resource: 'per-project token usage breakdown' with the metrics returned (cost, tokens, active days, models, date range). The 'per-project' framing implicitly separates it from tokmeter_providers and tokmeter_models, but no sibling is named explicitly.

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?

'Use this to see which projects are consuming the most AI resources' gives a usage context, but nothing states when NOT to use it or which sibling to pick instead (e.g. tokmeter_leaderboard, tokmeter_compare, tokmeter_providers). Usage is implied rather than directed.

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