Skip to main content
Glama

Detalhe de notícia da turma

get_news_detail

Retrieve the full text of a specific class news item using its news ID and class handle to read announcements and details from SIGAA.

Instructions

Full text of one class news item, by its id (from get_turma's news[].id).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "frontEndIdTurma": "<frontEndIdTurma>",
      "newsId": "<newsId>"
    },
    "name": "get_news_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
newsIdYesThe news id from get_turma (news[].id)
frontEndIdTurmaYesThe turma handle from get_portal

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.1

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden. It implies a read-only fetch and identifies the returned payload as the item's full text, but it says nothing about authentication, rate limits, error behavior for unknown ids, or whether the body can be truncated or empty.

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 zero waste: it identifies the resource, the unit (one item), the returned content (full text), and the id source. Nothing could be removed without losing information.

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?

For a simple two-parameter read tool with a fully documented schema and no output schema, the description adequately covers what the call returns and where the key input comes from. Only edge-case behavior (missing news, empty body) is left unstated, which is a minor gap at this complexity level.

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?

Schema description coverage is 100%, so both parameters are already documented in the schema. The description repeats the newsId provenance hint already present in the schema and adds no information about frontEndIdTurma, so the baseline of 3 applies.

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 resource and scope: the full text of exactly one class news item, retrieved by its id. That distinguishes it from the list-oriented siblings like get_turma, though it never names an alternative tool explicitly and the verb is implied rather than stated.

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?

It gives a useful prerequisite: the id must come from get_turma's news[].id, which tells the agent this is a follow-up call after listing news. There is no statement of when not to use it, no mention of what happens when a news item has no body, and no guidance tying frontEndIdTurma to get_portal.

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