Skip to main content
Glama

count_tokens

Read-onlyIdempotent

Estimate the token count of a text string using the cl100k_base approximation (~4 chars/token). Shows whether a text fits the context window of a model and what it costs. Returns token estimate, character count, and word count.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "input": "Hello world, this is a test."
    },
    "name": "count_tokens"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYesText to count tokens for

Output Schema

NameRequiredDescriptionDefault
charsNo
wordsNo
tokens_estimateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "input": "Hello world, this is a test."
      +  }
      +]
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds genuinely useful behavioral context beyond that: it discloses the estimation method (cl100k_base, ~4 chars/token), which tells the agent the result is an approximation rather than an exact tokenizer count.

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?

Three short sentences, front-loaded with the operation before the method and the return values. The clause about fitting a context window and cost slightly bleeds into sibling territory (estimate_llm_cost) but is not wasteful enough to penalize further.

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 one-parameter, read-only utility with an output schema and full annotation coverage, the description supplies everything essential, including the approximation caveat an agent needs to interpret results. Only the lack of routing guidance among overlapping siblings keeps it from a 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?

There is a single parameter with 100% schema description coverage, so the schema already explains that the input is the text to count. The description adds no format, size, or truncation guidance for the input, which matches the baseline of 3 when the schema carries the semantics.

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 and resource ("Estimate the token count of a text string") and names the tokenizer approximation (cl100k_base), so the operation is unambiguous. It does not, however, differentiate itself from close siblings such as context_window_check or token_budget_calculator, which cover overlapping concerns.

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?

Usage is only implied through the phrase "Shows whether a text fits the context window of a model and what it costs", which hints at a pre-flight sizing use case. There is no explicit when-to-use or when-not-to-use guidance and no mention of the sibling tools an agent should prefer for context-window or cost analysis.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.