Skip to main content
Glama

resumo_geral

Read-onlyIdempotent

Provides an overview of your latest study statistics spreadsheet by subject plus per-question exports, so you can review performance data in one place.

Instructions

Visão geral: última planilha de Estatísticas (por matéria) e/ou exports por questã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": "resumo_geral"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.1/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 and repeatability are covered. The description adds that it returns the latest statistics spreadsheet and/or per-question exports, which hints that results depend on what has been saved, but it says nothing about behavior when one or both sources are absent.

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 short sentence front-loaded with "Visão geral" and no filler. It is efficient, though so compressed that a reader must infer the verb and the return shape.

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?

The tool is parameterless, annotated, and has an output schema, so much of the burden is already carried by structured fields. What remains missing is a clear statement of how this overview relates to the sibling performance/export tools, which materially affects selection.

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

Parameters4/5

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

With zero parameters there is nothing to disambiguate, so the schema baseline of 4 applies. The description's note that both data sources are optional is consistent with the empty argument object.

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?

"Visão geral" plus the data sources named (última planilha de Estatísticas por matéria e/ou exports por questão) gives some substance, but the verb is only implied (retrieve) and the tool's scope overlaps visibly with siblings like desempenho, progresso and listar_exports without any cue to distinguish them.

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, no exclusion of alternatives, and no statement of prerequisites. The "e/ou" hints that either source may be present, but the agent is never told when to prefer this overview over desempenho or listar_exports.

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