Skip to main content
Glama

Intex Institute

Make all of it

make_everything

A LaTeX project in. The tagged PDF, an archival copy, the web page and the WCAG 2.1 report, from one build. 10 cents a page from the key's credit, against 13 one by one. 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": "make_everything"
  }
}

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
pagesNoPages of the PDF the project makes: what is billed.
cost_centsNoWhat this call cost.
credit_centsNoThe credit left on the key's account.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations, it discloses billing behavior (10 cents a page charged to the key's credit), an input size ceiling (24 MB), and a failure contract: unbuildable projects cost nothing and the response reports the offending file and line. Those are exactly the operational facts an agent needs before deciding to spend credits on a large build.

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?

Four short sentences with no filler, and the output list is front-loaded ahead of cost and limits. The clipped, verbless phrasing ('A LaTeX project in.') trades a little readability for density, but nothing is wasted.

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?

With a full output schema and 100% parameter coverage handled structurally, the description fills the remaining gaps an agent would care about: cost, size limit, and failure handling. It never states authentication or credit prerequisites explicitly (only 'the key's credit' in passing), which is the main omission for a billable tool.

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%, and the schema already explains main, files, archive, and binary_files in detail, so the description need not re-document them. Its only added semantic is the 24 MB project ceiling, which constrains the files/archive parameters without explaining their formats. 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?

The description names the input (a LaTeX project) and enumerates the four artifacts produced in one build (tagged PDF, archival copy, web page, WCAG 2.1 report), which cleanly separates it from the single-artifact siblings make_tagged_pdf and make_web_page. It is telegraphic and never literally states a verb like 'builds', so an agent must infer the action from 'from one build'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit selection rationale: 10 cents a page here versus '13 one by one', which tells the agent to prefer this tool when all four outputs are wanted and implies the siblings for single artifacts. It stops short of an explicit 'use X instead when you only need the PDF', but the cost comparison does that work implicitly.

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