Skip to main content
Glama

desempenho_assuntos

Read-onlyIdempotent

Analyze accuracy rates by subject or topic from TecConcursos and QConcursos data to reveal weak areas, rank performance, and filter by parent subject or minimum questions.

Instructions

Acertos por matéria/assunto.

fonte='tec': planilha de Desempenho mais recente do TecConcursos. nivel: 0 = matérias, 1 = assuntos de 1º nível (padrão), 2+ = subassuntos; None = todos. fonte='qconcursos': soma de todos os dias salvos; nivel 0 = disciplinas, 1 = assuntos. ordenar: 'fracos' (pior taxa primeiro, com Wilson para desempatar), 'fortes' ou 'volume'.

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

Input Schema

NameRequiredDescriptionDefault
fonteNotec
nivelNo
limiteNo
materiaNo
ordenarNofracos
min_questoesNo

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 a closed-world profile, so the safety burden is lifted. The description does add real behavioral context beyond them: data provenance per source ('planilha de Desempenho mais recente' vs 'soma de todos os dias salvos') and the ordering rule including the Wilson tiebreak. It omits truncation behavior for limite and what happens when no data exists for a source.

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?

The purpose leads, followed by compact per-source and per-parameter notes with no filler sentences. The fragmentary, line-broken phrasing is dense and readable, though the nivel explanation is split across two source clauses in a way that requires careful re-reading.

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 not be described, and the source/nivel interaction is well covered. However, three of six parameters are undocumented and there is no routing guidance, which leaves a six-parameter aggregation tool partly under-explained.

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 description must carry all parameter meaning. It does this well for fonte, nivel (including the source-specific level semantics and None) and ordenar (enum-like values with tiebreak behavior), but leaves limite, materia and min_questoes entirely unexplained.

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?

"Acertos por matéria/assunto" states a specific measure (correct-answer counts) and a specific grouping (subject/topic), so the agent knows what comes back. It never names or contrasts with siblings like desempenho or pontos_fracos, so differentiation is left to inference.

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?

The description explains per-source semantics but gives no when-to-use or when-not-to-use guidance relative to alternatives such as desempenho or pontos_fracos. An agent cannot tell from this text which tool to pick for a weak-topics question without comparing schemas.

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