Skip to main content
Glama

Knowità – Execution Way©

Contatti Knowità

contatti_knowita
Read-onlyIdempotent

Recapiti ufficiali di Knowità per richieste di consulenza, formazione o informazioni.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is fully covered by structured metadata. The description adds only that the data is 'official' contact information, which is useful framing but does not disclose what channels are returned (email, phone, form) or the response shape.

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 noun phrase that conveys resource, authority ('ufficiali'), and intended use with no filler. Nothing in the sentence could be removed without losing meaning.

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 zero-parameter, read-only lookup whose safety semantics are fully carried by annotations, the description is nearly sufficient. The one gap is that with no output schema the agent cannot know exactly what 'recapiti' includes, which a brief mention of the returned channels would have closed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline of 4 applies. There is no argument syntax an agent could get wrong, and nothing further is required from the description on this dimension.

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 identifies a specific resource — Knowità's official contact details ('recapiti ufficiali') — and the kind of requests they serve (consulting, training, information). An agent can readily tell it returns contact information rather than events, news, or services, but the description makes no explicit reference distinguishing it from sibling company-info tools.

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?

The phrase 'per richieste di consulenza, formazione o informazioni' implies the situations where these contacts are relevant, giving an implicit when-to-use signal. There is no explicit statement of when to prefer this over siblings like trova_servizi or presenta_knowita, nor any exclusions.

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.