Skip to main content
Glama

Knowità – Execution Way©

Cerca nel Content Hub

cerca_contenuti
Read-only

Cerca articoli, approfondimenti, casi di successo ed eventi pubblicati su knowita.it. Restituisce titolo, link, data ed estratto.

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": {
      "testo": "<testo>"
    },
    "name": "cerca_contenuti"
  }
}

Input Schema

NameRequiredDescriptionDefault
testoYesParole da cercare.
limiteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description does add value by naming the returned fields (titolo, link, data, estratto), which matters because there is no output schema, but it says nothing about result ordering, total counts, or what 'limite' truncation means for the caller.

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?

Two sentences, both front-loaded: the first covers scope and content types, the second covers the return shape. No filler, no repetition of the title.

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 two-parameter search tool with annotations present, the description covers what is searched and what comes back, which is more than most. The remaining gap is the missing explanation of result limiting via 'limite' and whether results are ranked, but overall an agent has enough to call it correctly.

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?

With only 50% schema description coverage, the description does not compensate: 'testo' remains an unqualified 'Parole da cercare' (no indication of multi-word AND/OR behavior or full-text matching), and 'limite' is never mentioned in the description. The schema at least supplies default, minimum and maximum for 'limite', which keeps this at a minimum-viable 3 rather than lower.

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 verb ('Cerca') and enumerates the resource types it covers (articoli, approfondimenti, casi di successo, eventi) scoped to knowita.it, which lets an agent recognize it as a site-wide content search. It stops short of distinguishing itself from siblings such as eventi_knowita or ultime_news, even though it explicitly covers events and news-like content.

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?

The description says what is searchable but gives no when-to-use framing, no exclusions, and never mentions when a sibling tool would be preferable (e.g., dedicated events or news listings). An agent must infer usage entirely from the verb.

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.