Skip to main content
Glama

ira

Read-onlyIdempotent

Queries semester-by-semester Academic Performance Index trends for a student, comparing individual and overall results with the course average and standard deviation.

Instructions

Consulta a evolução semestral do Índice de Rendimento Acadêmico (IRA Individual e Geral) do estudante em relação à média e desvio padrão do curso.

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

Input Schema

NameRequiredDescriptionDefault
atualizarNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered and the description need not repeat it. What is missing is behavior tied to the sole parameter 'atualizar': whether toggling it forces a fresh fetch from the source system, hits a rate limit, or changes latency/caching. Given an option literally named 'update' on a read-only tool, some disclosure would materially help.

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 front-loaded sentence with no filler, and the scope (individual vs. geral, versus course mean/std dev) is stated compactly. Nothing is wasted, though the sentence could have spent a few words on 'atualizar' instead of none.

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 the return values do not need explaining, and the annotations cover the safety profile. For a one-parameter tool that is nearly sufficient, but the complete silence on the only parameter leaves a real gap an agent would have to resolve by trial.

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% and the single parameter 'atualizar' (boolean, default false) is never mentioned in the description. The description therefore adds no meaning beyond the schema, and the agent must guess whether 'atualizar' triggers a remote refresh, a cache bypass, or nothing user-visible.

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 specific verb (consulta) and a well-defined resource (evolução semestral do IRA Individual e Geral), and it clarifies what the measure is compared against (média e desvio padrão do curso). That rescues an otherwise opaque tool name ('ira'). It does not explicitly differentiate itself from near neighbors like notas or progresso, so it stops short of a 5.

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 mention of prerequisites (e.g., must the student be enrolled, is data per-semester or cumulative), and no reference to alternatives such as notas or progresso. The description only says what data is returned, leaving selection between this and sibling academic tools to inference.

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