Skip to main content
Glama

questoes_erradas

Read-onlyIdempotent

Retrieve recently missed exam questions, newest first, to build a review list. Filter by subject, topic, board, year, or limit results for focused study.

Instructions

Questões que você errou, mais recentes primeiro — para montar revisão.

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

Input Schema

NameRequiredDescriptionDefault
anoNo
bancaNo
limiteNo
assuntoNo
materiaNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already establish read-only, idempotent, closed-world behavior, while the description usefully adds recent-first ordering and user-specific error-history scope. It does not clarify the source or extent of that history, empty-result behavior, or truncation, though the output schema removes the need to describe the return structure.

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?

A single compact sentence front-loads the resource, ordering, and intended use without filler. Its brevity is effective, although the missing parameter guidance must be compensated elsewhere.

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?

For a simple read with only optional parameters and an output schema, the description is sufficient for a basic unfiltered call and clarifies result ordering. It remains incomplete for reliable filtered invocation because all five parameters are undocumented and the boundary with nearby review and analytics tools is unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description explains none of ano, banca, limite, assunto, or materia. It does not state whether filters combine, what values the string filters accept, or how limite affects the recent-first results.

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?

The description clearly identifies the resource and personalized scope: questions the user answered incorrectly, ordered most recent first. It does not explicitly distinguish this retrieval tool from siblings such as pontos_fracos or buscar_questao.

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?

The phrase "para montar revisão" provides a concrete use case: assembling a review session. It gives no when-not guidance or explicit alternative for aggregate weakness or performance analysis.

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