Skip to main content
Glama
Sign In
enem-mcp

enem-mcp

by jpmamededs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Ver questão

obter_questao
Read-only

Retrieves a complete ENEM exam question by year and number, including alternatives, figures, and an optional answer key for study and review.

Instructions

Retorna o enunciado completo, as alternativas e as imagens (gráficos, tirinhas, mapas) de uma questão do ENEM.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ano": "<ano>",
      "numero": "<numero>"
    },
    "name": "obter_questao"
  }
}

Input Schema

NameRequiredDescriptionDefault
anoYesAno da prova, ex.: 2022
idiomaNoIdioma para as questões 1-5 de língua estrangeira
numeroYesNúmero da questão na prova
incluir_imagensNoAnexa as figuras da questão para análise visual
mostrar_respostaNoSe true, inclui o gabarito

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful scope about what content is returned as text (enunciado, alternativas) versus attached figures, but says nothing about the optional gabarito or the idioma-dependent behaviour for questions 1-5, both of which materially change the output.

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?

A single front-loaded sentence with no filler, and the return payload is stated before the qualifier. It could be marginally tighter, but every clause carries information.

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 five parameters, no output schema and thin annotations, the description does the core job of telling the agent what comes back (statement, options, figures). It leaves the answer-key path and the foreign-language handling unexplained, so it is solid but not fully complete for a tool whose output shape is otherwise undocumented.

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 ano, numero, idioma, incluir_imagens and mostrar_resposta are all documented in the schema; baseline 3 applies. The description only loosely echoes incluir_imagens by mentioning imagens, and adds no syntax, format or edge-case detail (e.g. maximum question number, null idioma behaviour) beyond the schema.

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 ('Retorna') and resource ('questão do ENEM') and enumerates the payload: enunciado completo, alternativas e imagens. An agent can distinguish it from answer-only or search tools conceptually, but the description never names the nearby siblings (obter_resposta, buscar_questoes) that overlap most.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not guidance: nothing tells the agent to pick this over buscar_questoes for lookup or obter_resposta when only the gabarito is needed. The only hint is the required ano/numero, which implies fetching a known question, but that is inference rather than stated 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