Skip to main content
Glama

progresso

Read-onlyIdempotent

Tracks study progress over time, overall and by subject, from TecConcursos spreadsheets or QConcursos daily data to show how performance changes.

Instructions

Evolução no tempo, no total e por matéria.

fonte='tec': um ponto por planilha exportada (cada uma cobre o período escolhido no site). fonte='qconcursos': um ponto por dia coletado.

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

Input Schema

NameRequiredDescriptionDefault
fonteNotec
materiaNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.3/5.0
Behavior4/5

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

The annotations already establish that the tool is read-only, idempotent, and closed-world, so the description need not repeat that safety profile. What the description adds is substantive: the granularity of the output series differs by source, with 'tec' producing one point per exported spreadsheet, each covering the period chosen on the site, and 'qconcursos' producing one point per collected day. That explains why two series with the same subject may not be comparable point-for-point, which is genuine behavioral context that the annotations cannot express.

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 header line followed by a bullet-style breakdown of each source value, with zero filler and the definition of the metric front-loaded. The terse wording of 'Evolução no tempo, no total e por matéria' is slightly cryptic on its own, but the structure overall is efficient and easy to scan.

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 is present and the tool is a simple two-parameter read, which lowers the burden. Even so, the description leaves out the default for 'fonte' and the effect of 'materia' (whether it filters or breaks down the series), which are exactly the details an agent needs to invoke the tool correctly. That gap is moderate rather than severe given the supplied output schema.

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 the parameter semantics. It documents both meaningful values for 'fonte' ('tec' and 'qconcursos') and their operational consequences, which is better than nothing. However, it omits that 'fonte' defaults to 'tec', and it never explains what 'materia' does; the phrase 'por matéria' only hints that it filters or splits the series, without saying which.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the resource and scope: evolution over time, in total, and broken down by subject. But it never uses an explicit verb such as 'retorna' (returns) or 'consulta' (queries), and it draws no distinction from close siblings like 'desempenho', 'desempenho_assuntos', and 'resumo_geral', which also sound like performance aggregations. The agent can infer that this is a progress time series, but it cannot confirm how it differs from those siblings by reading the definition.

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?

The two bullets about 'fonte' imply usage by explaining what one data point means for each source (per exported spreadsheet versus per collected day), which helps an agent realize that the granularity changes with the source. However, the definition never says when to call this tool instead of 'desempenho' or 'desempenho_assuntos', and it states no exclusions. Usage must be inferred from the tool name and the point semantics.

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