Skip to main content
Glama

Intex Institute

Count a project

count_project
Read-onlyIdempotent

A LaTeX project in. Its pages, formulas, figures and tables out, with what each tool would cost for it, in cents. Free, with a key. Up to 24 MB for the project. A project that cannot be built costs nothing; the answer gives the file and line.

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

Input Schema

NameRequiredDescriptionDefault
mainNoThe path of the main .tex file. Needed only when the project has more than one.
filesNoThe project's text files by their path inside the project, each file's whole text: the .tex files, and any .bib, .bbl, .sty, .cls or .tikz of your own. Example: {"main.tex": "\\documentclass{article}...", "chapters/one.tex": "..."}.
archiveNoInstead of files: the whole project as one .zip or .tar.gz, base64-encoded.
binary_filesNoFigures and other binary files by path, each base64-encoded. PNG and JPEG are placed as they are; a PDF, EPS or SVG figure is answered with its name, to be saved as a PNG.

Output Schema

NameRequiredDescriptionDefault
pagesNo
tablesNo
figuresNo
formulasNo
cost_centsNoWhat each paid tool would cost for this project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive and closed-world behavior, so the bar is lower, yet the description adds real value: it discloses the 24 MB project limit, the need for an API key, and that an unbuildable project is not charged and returns the offending file and line. It stops short of saying whether counts are approximate or how binaries affect pricing.

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?

Five short sentences with no filler; the input-output framing, the cost note and the size limit are front-loaded. Nothing is repeated from the schema.

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?

An output schema exists, so return values need no explanation, and the description covers cost model, auth, size limit and build-failure behavior. The one gap is not relating the cost figures to the sibling make_* tools an agent would weigh them against.

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%, so the baseline is 3. The description mentions the 24 MB ceiling but adds nothing about when to use `files` versus `archive`, how `main` is resolved, or how supplied binary figures are handled — all of which the schema already documents.

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 names the resource (a LaTeX project) and the output (page, formula, figure and table counts plus a per-tool cost in cents), which is enough to distinguish it from the make_* siblings that produce documents. The inverted, telegraphic phrasing ('A LaTeX project in. Its pages ... out') is readable but slightly slows recognition of the verb.

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: the per-tool cost output suggests running this before a build to estimate expense, and 'free, with a key' hints at the auth requirement. There is no explicit statement of when to prefer this over check_accessibility or make_everything, and no when-not guidance.

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.

Resources