Skip to main content
Glama

pontos_fracos

Read-onlyIdempotent

Identifies weak spots in study performance by grouping questions and filtering out small samples, so you can focus on groups with the lowest accuracy rates.

Instructions

Grupos com pior taxa de acerto, ignorando os com poucas questões (min_questoes).

Inclui indice_confianca (limite inferior de Wilson) para desempatar amostras pequenas.

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

Input Schema

NameRequiredDescriptionDefault
bancaNo
limiteNo
materiaNo
agrupar_porNoassunto
min_questoesNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds real value by disclosing the small-sample filtering rule and that results carry an 'indice_confianca' Wilson lower bound used for tie-breaking, which is behavior an agent cannot infer from the schema. It stops short of describing ordering direction (ascending by accuracy), pagination, or how many rows 'limite' yields.

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 with the core behavior front-loaded and the tie-breaking detail appended, with no filler. It is tight, though it spends a line on Wilson-bound internals while leaving four parameters unexplained.

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 safety profile is covered by annotations. However, for a five-parameter aggregation tool with zero schema coverage, the omission of valid values for 'agrupar_por' and the effect of 'limite'/'banca'/'materia' leaves the definition under-specified for correct invocation.

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

Parameters2/5

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

Schema description coverage is 0% across five parameters, so the description must carry the burden and it only explains 'min_questoes' explicitly. The meaning and accepted values of 'agrupar_por' (default 'assunto'), 'limite', 'banca', and 'materia' remain undefined, leaving the agent to guess valid grouping dimensions.

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 (group/rank) and resource ('grupos com pior taxa de acerto'), so the agent knows it returns worst-performing groups rather than a general performance summary. It does not name a sibling like desempenho or desempenho_assuntos to differentiate, but the purpose itself is unambiguous.

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 says what it produces but not when to choose it over siblings such as desempenho, desempenho_assuntos, or questoes_erradas. There is no explicit when-to-use or exclusion guidance; the only conditional it gives ('ignorando os com poucas questões') is a filtering rule, not usage guidance.

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