Skip to main content
Glama

Informazioni su Interfibra

informazioni_azienda
Read-onlyIdempotent

Dati dell'azienda, contatti e orari, significato delle tecnologie (FTTH, FTTC, FWA), prezzo bloccato, costi di uscita, tempi di attivazione, fatturazione, pagamenti, come si conclude la sottoscrizione e, finché dura, il voucher di Open Fiber a cui Interfibra aderisce (buonoOpenFiber).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 the safety profile is fully covered by structured data. The description adds little behavior beyond that: it lists what topics exist, without saying whether the content is static or fetched, whether it varies by customer, or how current pricing/activation figures are. That is acceptable given the annotation coverage but is not value-adding context.

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?

It is a single sentence with no filler words, and the most important item (company data, contacts, hours) is front-loaded. The long comma-separated tail of topics is dense but each item does describe real content scope, so little is wasted; a short lead-in verb or light grouping would make it easier to scan.

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?

With no input parameters and no output schema, the description carries the burden of telling the agent what information is available, and it does so by enumerating the covered topics in detail. The main residual gap is the unresolved overlap with the buono_open_fiber sibling, which an agent would need in order to route voucher questions correctly.

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 there is no parameter semantics for the description to explain; the schema itself is trivially complete. Baseline 4 applies, and the topic list usefully signals the breadth of what a single call returns.

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 enumerates a concrete and distinctive content scope: company data, contacts and hours, technology meanings (FTTH/FTTC/FWA), locked price, exit costs, activation times, billing, payments and subscription closure. That lets an agent separate it from elenco_offerte, dettaglio_offerta and verifica_copertura without opening any schema. It loses a point because no explicit verb states that this is a retrieval/FAQ tool, and the mention of the Open Fiber voucher does not clarify the relationship with the sibling buono_open_fiber.

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: an agent can infer 'use this for general company/FAQ questions', but there is no explicit when-to-use statement and no exclusions. The one place guidance was really needed - the voucher topic that overlaps with the sibling buono_open_fiber - is left unresolved, since the description only says the voucher is covered 'finché dura' (while it lasts).

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.

Resources