Skip to main content
Glama

Knowità – Execution Way©

Ultime news Knowità

ultime_news
Read-onlyIdempotent

Le news più recenti pubblicate nel Content Hub di Knowità (approfondimenti su AI, sostenibilità, budgeting, change management e report degli eventi).

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

Input Schema

NameRequiredDescriptionDefault
limiteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety and reproducibility are covered. The description adds the useful scope detail that results are the newest publications across defined topic areas, but says nothing about ordering guarantees, recency window, whether the feed can be empty, or result shape.

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?

One compact sentence, front-loaded with the core resource and followed by a useful enumeration of topics. No filler or repetition of the title. Slightly dense parenthetical but earns its space.

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?

For a read-only, no-required-param tool with full safety annotations, most of what an agent needs is present. However, with no output schema the description could have said what a result item looks like (title/date/link) and how the limit interacts with the feed; those gaps keep it at minimum-viable.

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?

The single parameter 'limite' is never mentioned in the description, so coverage is 0% and the schema carries everything (integer, default 5, min 1, max 10). The constraints make it mechanically usable, but the description does not compensate for the coverage gap by explaining what the limit counts or what happens at the cap.

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 resource ('le news più recenti pubblicate nel Content Hub') and even enumerates the topical domains covered (AI, sostenibilità, budgeting, change management, eventi). An agent can tell this apart from cerca_contenuti as a 'latest items' feed rather than a search, though the sibling is never named. The verb is implicit in 'pubblicate' but the intent 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 Guidelines3/5

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

Usage is only implied: fetch this when the user wants recent/aggregate Knowità content. There is no explicit statement of when to prefer this over cerca_contenuti or eventi_knowita, and no exclusions or prerequisites. Adequate for a simple feed-style tool but leaves routing to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.