Skip to main content
Glama

buscar_questao

Read-onlyIdempotent

Search study questions by keywords across code, subject, topic, statement, and answer choices, with optional filters for board and subject and a result limit.

Instructions

Busca por palavras (todas precisam aparecer) no código, matéria, assunto, enunciado e alternativas.

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": {
      "termo": "<termo>"
    },
    "name": "buscar_questao"
  }
}

Input Schema

NameRequiredDescriptionDefault
bancaNo
termoYes
limiteNo
materiaNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.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, idempotentHint and openWorldHint=false, so safety is covered. The description adds genuinely useful behavior — that the match is conjunctive (all terms must appear) and which fields are searched — but says nothing about result ordering, pagination, or what happens on zero matches.

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; the matching rule is placed inline where it matters most. It is efficient, though it packs several distinct facts into one clause chain.

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?

An output schema exists, so return values need no explanation. For a four-parameter search tool, however, the definition leaves three parameters undocumented and gives no sense of how paging via limite behaves, leaving meaningful gaps for an agent composing a query.

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 0%, so the schema only gives names and defaults. The description clarifies the semantics of 'termo' (multi-word, AND-matched across five fields), which is real added value, but banca, materia and limite are left completely unexplained — and listing 'matéria' as a searched field arguably muddies whether the materia parameter is a filter or a search target.

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 (busca) and resource (questão) plus the fields searched — código, matéria, assunto, enunciado, alternativas — so the agent knows this is a keyword search over question content. It does not distinguish itself from siblings such as questoes_erradas or desempenho_assuntos, which is the only thing keeping it from a 5.

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 guidance at all: no mention of when keyword search is preferable to the sibling tools, no prerequisites, and no exclusions. The parenthetical 'todas precisam aparecer' is an implicit hint about search strictness but not routing guidance.

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