Skip to main content
Glama

Knowità – Execution Way©

Trova i servizi Knowità

trova_servizi
Read-onlyIdempotent

Trova i servizi Knowità adatti a un'esigenza o sfida aziendale descritta a parole (es. "introdurre gli OKR", "bilancio di sostenibilità", "NIS2", "agenti AI", "marginalità per cliente"). Restituisce servizio, area, business unit e pagina di riferimento.

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": {
      "esigenza": "<esigenza>"
    },
    "name": "trova_servizi"
  }
}

Input Schema

NameRequiredDescriptionDefault
limiteNo
esigenzaYesL'esigenza o la sfida aziendale, in italiano.
business_unitNoFacoltativo: limita la ricerca a una business unit.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive behavior, so the safety profile is covered. The description adds value by naming the returned fields (servizio, area, business unit, pagina di riferimento), which matters since no output schema exists, but it says nothing about match semantics (semantic vs keyword), ranking, or what happens when nothing matches.

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?

Two sentences with no filler: the core action and input form come first, followed by the return fields. It could be tightened only marginally, e.g. by folding the return-field list into a clause about what the agent should expect.

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 three-parameter read-only search tool with no output schema, the description covers purpose, input examples, and return fields — enough to call it correctly. The remaining gap is behavioral detail on matching/ranking and empty results, which is minor for this tool class.

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 coverage is 67%, so most parameters are documented in the schema itself, including business_unit's enum values and limite's bounds. The description only reinforces the esigenza parameter by giving example free-text needs and specifying the input language indirectly; it adds no meaning for limite or business_unit beyond the schema.

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 verb and resource ("Trova i servizi Knowità") and clarifies the input shape with concrete example needs ("introdurre gli OKR", "NIS2", "agenti AI"). It distinguishes itself by scope (services) rather than by naming the closest sibling such as cerca_contenuti, so sibling differentiation is implicit only.

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 implied rather than stated: the agent can infer it should call this when a user expresses a business need in free text, helped by the example phrasings. There is no explicit when-not guidance and no alternative tool is named for cases like exact keyword lookup or content search.

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.