Skip to main content
Glama

desempenho

Read-onlyIdempotent

Calculates grouped accuracy rates by subject, topic, board, or year from study data, applying optional filters to reveal weak areas and track progress.

Instructions

Taxa de acerto agrupada por materia, assunto, banca, orgao, cargo ou ano.

Filtros opcionais restringem as questões consideradas (ex.: agrupar_por='assunto', materia='penal').

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

Input Schema

NameRequiredDescriptionDefault
anoNo
bancaNo
materiaNo
agrupar_porNomateria
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
Behavior2/5

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

Annotations already declare readOnly, idempotent and closed-world, and the description adds no behavior beyond that surface statement. It never explains aggregation semantics such as whether the accuracy rate is weighted by question count, or what happens to groups that fall below the min_questoes threshold — the one behavior an agent most needs to interpret 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?

Two short sentences: the grouping capability is front-loaded and the second sentence covers filtering with a concrete example. No padding, though the example could have been used to illustrate the unexplained min_questoes parameter instead of repeating known fields.

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-shape explanation is rightly omitted, and the read-only annotations cover the safety profile. However, for a five-parameter aggregation tool with zero schema descriptions, the definition omits the threshold parameter's effect and the full set of valid agrupar_por values, leaving real gaps.

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 carries the full burden, and it only partially does so: it clarifies the role of agrupar_por and materia with an example, but leaves ano, banca and especially min_questoes (a filtering threshold on group size) undefined. It also lists orgao and cargo as grouping values without any corresponding filter parameters, which is not reconciled.

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 states a concrete measure (taxa de acerto) and enumerates the grouping dimensions (materia, assunto, banca, orgao, cargo, ano), which is far more specific than the bare name 'desempenho'. It does not distinguish itself from the very similar sibling 'desempenho_assuntos', so the agent must guess which aggregation tool to use.

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 implied rather than stated: it explains that optional filters narrow the question set and gives one worked example (agrupar_por='assunto', materia='penal'). There is no explicit when-to-use versus 'desempenho_assuntos' or 'pontos_fracos', and no guidance on when the filters should be left empty.

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