Skip to main content
Glama

portal

Read-onlyIdempotent

Retrieves a student's institutional summary, including course, status, completion progress, current-semester classes, and upcoming activities, with an optional refresh.

Instructions

Obtém o resumo institucional do estudante no Portal do Discente (curso, status, integralização, turmas do semestre e atividades próximas).

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

Input Schema

NameRequiredDescriptionDefault
atualizarNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

A3.5/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. The description adds that the result is a composite summary spanning several data domains, which is useful, but it says nothing about whether the data is cached, what "atualizar" triggers, or latency/cost of the aggregated fetch.

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 the verb and resource first, then the returned fields in parentheses. Dense but with no filler; only the enumerated field list could be trimmed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 tool has one optional parameter plus read-only annotations. The definition is complete enough to call correctly; the remaining gap is the semantics of the refresh flag.

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?

There is a single parameter, "atualizar" (boolean, default false), and schema description coverage is 0% — neither the schema nor the description explains what refreshing means or when it should be set. The description compensates only indirectly by implying fresh institutional data.

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 gives a specific verb ("Obtém") and resource ("resumo institucional do estudante") and enumerates the contents: curso, status, integralização, turmas do semestre, atividades próximas. This makes it identifiable as an aggregate overview rather than a single-domain tool, though it never names the sibling tools (status, turmas, agenda) it overlaps with.

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 only implied: the phrase "resumo institucional" suggests a one-stop overview, so an agent can infer it is a good first call. There is no explicit when-to-use/when-not guidance and no statement about how it relates to sibling tools that return the same slices of data.

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