Skip to main content
Glama
Sign In
enem-mcp

enem-mcp

by jpmamededs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Criar simulado

criar_simulado

Creates randomized ENEM practice exams by topic, discipline, or year, optionally as a printable PDF, and returns an exam ID for later correction.

Instructions

Cria um simulado com questões aleatórias do ENEM por tema/disciplina/ano, opcionalmente em PDF. Use corrigir_simulado com o ID retornado para corrigir.

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

Input Schema

NameRequiredDescriptionDefault
anosNoAnos das provas. Vazio = todos
temaNoPalavras-chave do tema. Separe alternativas com vírgula, ex.: 'genética, DNA, hereditariedade'
idiomaNoIdioma das questões de língua estrangeiraingles
gerar_pdfNoGera um PDF para impressão/download com questões, imagens e folha de respostas
disciplinaNoÁrea do conhecimento
quantidadeNoNúmero de questões
evitar_repetidasNoEvita questões que já saíram em simulados anteriores
incluir_gabarito_no_pdfNoAdiciona ao final do PDF uma página 'GABARITO ABAIXO' e as questões resolvidas

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the write nature is covered. The description adds one piece of genuine behavioral context — that an ID is returned and later consumed by `corrigir_simulado` — but says nothing about whether the simulado is persisted/listed, whether generation is slow, or what the response otherwise contains.

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?

Two short sentences, front-loaded with the core action and leaving the next-step hint at the end. Slight redundancy in restating tema/disciplina/ano, which the schema already defines, keeps it from being maximally tight.

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 8 parameters, all optional, and no output schema, the description covers the essential creation story and the ID handoff to correction. Minor gaps remain about what is returned besides the ID and how this differs from `criar_simulado_revisao`.

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 is richer than the description: it documents the tema comma-separated keyword syntax, the idioma enum, quantidade's 1–90 bounds, evitar_repetidas and incluir_gabarito_no_pdf. The description merely summarizes three of the eight parameters, adding no meaning beyond the schema, 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 specific verb and resource ('Cria um simulado') plus the selection axes (tema/disciplina/ano) and an optional artifact (PDF). It does not differentiate itself from the sibling `criar_simulado_revisao`, which by name sounds like a very similar creation tool, so the agent must infer the difference.

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?

Provides a useful downstream routing hint: use `corrigir_simulado` with the returned ID to correct the simulado. However, there is no explicit when-to-use vs. `criar_simulado_revisao` or `buscar_questoes`, and no prerequisites or exclusions are given.

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