Skip to main content
Glama
geo-sapiens

Coletum MCP Server

Official
by geo-sapiens
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

salvar_modelo

Save a reusable PDF template locally by name, including forms, mapping, variables, files, and fonts, to generate future Coletum PDFs without rebuilding the layout.

Instructions

Salva um modelo de PDF na máquina do cliente, para reusar só pelo nome em gerar_pdf_modelo.

Grava // com modelo.typ, modelo.json (descrição, formulários, mapeamento, datas), arquivos/ e fontes/. Não sobrescreve sem substituir=true. Modelos embutidos não podem ser trocados. Não chama a API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
logoNoLogo do cliente (PNG, JPG, SVG), guardado como arquivos/logo.<ext>: o template usa "/arquivos/logo.png" (ou dados.documento.logo).
nomeYesNome curto do modelo, minúsculas, números, _ ou - (ex.: vistoria_obra). É o que o cliente vai dizer: 'gera no modelo da obra'.
fontesNoArquivos de fonte (.ttf, .otf) que o template usa, guardados em fontes/ do modelo.
arquivosNoArquivos locais que o template usa (logo, imagens), guardados em arquivos/ do modelo.
aparenciaNoAparência padrão do modelo (mesmo formato de aparencia em gerar_pdf_modelo); a chamada pode trocar.
descricaoNoPara que serve, em uma frase (quem lê, que documento é).
variaveisNoTextos fixos do cliente que não vêm do formulário (ex.: {"obra": "...", "contratante": "..."}), usados como padrão em documento.variaveis; a chamada de gerar_pdf_modelo pode trocar.
mapeamentoNoMapeamento confirmado: rótulo do modelo do cliente para o campo do formulário (mesmo formato de gerar_pdf_modelo).
substituirNoTrocar um modelo que já existe com esse nome. Confirme com o cliente antes.
formulariosNoId(s) do(s) formulário(s) a que o modelo se aplica.
template_typstYesTexto do template Typst aprovado (o mesmo que gerou a amostra).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A4.4/5.0
Behavior5/5

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

Despite annotations declaring a non-destructive write, the description discloses what actually gets written to disk (modelo.typ, modelo.json, arquivos/, fontes/), the overwrite guard (substituir=true), the immutability of built-in models, and that no API call is made. This is behavior an agent cannot infer from readOnlyHint/destructiveHint/openWorldHint alone.

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?

Three tight sentences, front-loaded with the purpose and the downstream consumer, then the on-disk effect and the two safety rules. No filler.

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 an 11-parameter mutation tool with no output schema, the description covers destination layout, overwrite policy, built-in model restrictions, and absence of API calls. Missing only an explicit return/confirmation statement, which is minor since there is no output schema.

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 baseline is 3. The description reinforces the substituir semantics (no overwrite without substituir=true) and the destination path tied to nome, but adds little beyond what the per-property descriptions already state.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (salva) and resource (modelo de PDF), names the sibling that consumes the result (gerar_pdf_modelo), and distinguishes itself from read-only siblings like listar_modelos. An agent can identify the tool's role without opening the schema.

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?

Explains the reason to use it (reuse by name later in gerar_pdf_modelo) and gives two concrete conditions: no overwrite without substituir=true, and built-in models cannot be swapped. It stops short of an explicit when-not/alternative routing, but the constraints are practical guidance.

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

Deploy Server

Other Tools