Skip to main content
Glama

Intex Institute

Make an accessible web page

make_web_page

A LaTeX project in. One web page out from the same reading as the PDF: its HTML, formulas in MathML, and its figures. 4 cents a page from the key's credit. 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_web_page"
  }
}

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

A3.8/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing cost (4 cents a page from the key's credit), an input cap (24 MB), and failure behavior (unbuildable projects are free, the answer reports file and line). It does not say what happens to prior output or where the page is placed, which keeps it from a 5.

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, front-loaded with the input/output contract, then cost, then limits, then failure semantics. No sentence is redundant, and the clipped style stays readable.

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 an output schema present, return values need not be explained, and the description still covers cost, size limits, and error reporting for a moderately complex converter. Only the question of where/whether the generated page persists is left unaddressed.

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 the four parameters are already fully documented, including the files/archive/binary_files distinction and the PDF/EPS/SVG figure caveat. The description adds only the project-level 24 MB limit and nothing per-parameter, so the 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 concrete transformation ('A LaTeX project in. One web page out') and names the artifact details (HTML, MathML formulas, figures), which is enough to distinguish it from a PDF-producing sibling. It stops short of explicitly naming an alternative tool, so the differentiation relies on the 'from the same reading as the PDF' contrast.

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 implied rather than stated: an agent can infer it is for producing an accessible web page instead of a PDF. There is no explicit when-to-use/when-not-to-use guidance and no reference to make_everything or check_accessibility, leaving the routing decision partly to inference.

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