Skip to main content
Glama
Sign In
enem-mcp

enem-mcp

by jpmamededs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Buscar questões

buscar_questoes
Read-only

Search ENEM exam questions by keyword, discipline, and year to build targeted study sets. Returns a summarized list of matching questions from official exams.

Instructions

Busca questões do ENEM por tema (palavra-chave), disciplina e/ou ano. Retorna uma lista resumida.

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

Input Schema

NameRequiredDescriptionDefault
anosNoAnos das provas. Vazio = todos
temaNoPalavras-chave buscadas no texto da questão. Separe alternativas com vírgula, ex.: 'fotossíntese, clorofila'
idiomaNoIdioma das questões de língua estrangeiraingles
limiteNo
disciplinaNoÁrea do conhecimento

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=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds one useful behavioral fact — the return is a summarized list rather than full questions — but says nothing about pagination, default limits, result ordering, or truncation, which matter for a search tool.

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?

Two short sentences, zero filler, with the search scope front-loaded and the return shape stated second. Nothing is repeated or padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With five optional parameters, no output schema, and moderate annotation coverage, the description should say more about what 'lista resumida' contains and how 'limite' behaves. It is adequate to identify the tool but leaves gaps an agent would need to close by trial.

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 80%, so the schema already explains anos, tema (including comma-separated alternatives), idioma and disciplina. The description only restates these filter dimensions at a high level and adds no semantics for the undocumented 'limite' parameter, so it stays at the baseline.

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 (search ENEM questions) plus the filterable dimensions (tema, disciplina, ano) and the shape of the result ('lista resumida'). It does not distinguish itself from siblings such as obter_questao or questao_aleatoria, so an agent must infer the boundary itself.

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 only implied: the 'e/ou' phrasing signals that filters can be combined, but there is no explicit when-to-use, when-not-to-use, or named alternative for fetching a single known question. The agent is left to infer that this is the exploratory/list path.

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