Skip to main content
Glama

pendencias

Read-onlyIdempotent

Queries UFC course-completion pending requirements, including outstanding credit hours, ENADE, and library obligations, with an option to refresh results.

Instructions

Consulta o relatório de pendências para conclusão de curso (carga horária pendente, ENADE e biblioteca).

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

Input Schema

NameRequiredDescriptionDefault
atualizarNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

B3.3/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 fully covered without help from the description. The description adds value by specifying the report's content areas, but says nothing about whether results are cached or live, and nothing about the effect of forcing an update.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with the resource stated first and the parenthetical reserved for concrete content areas. Nothing redundant is included.

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-value detail is correctly omitted, and the read-only nature is covered by annotations. The remaining material gap is the undocumented 'atualizar' switch, which is decision-relevant for how the agent invokes the tool.

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% for the single parameter 'atualizar', and the description never mentions it at all, so the agent cannot tell from prose whether setting it true forces a fresh computation, bypasses a cache, or has side effects. With one undocumented parameter, the description fails to compensate for the coverage gap.

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 names a specific verb plus resource ('Consulta o relatório de pendências para conclusão de curso') and enumerates the contents (carga horária pendente, ENADE, biblioteca), so the agent knows exactly what data comes back. It does not distinguish itself from potentially overlapping siblings such as 'progresso' or 'status', which keeps it from 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Use is implied by the 'para conclusão de curso' scoping, so an agent can infer this is for graduation-requirement checks. There is no explicit statement of when to prefer this over 'progresso'/'status' and no note about when a refresh is warranted, leaving guidance inferential.

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