Skip to main content
Glama

Catalogo prodotti Virtech

Contatti ufficiali di Virtech

get_virtech_contact
Read-onlyIdempotent

Restituisce l'indirizzo della pagina Contattaci e l'email pubblica di Virtech.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
urlYes
emailYes

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=true, idempotentHint=true, destructiveHint=false and closed-world behavior, so the safety profile is fully covered by structured data. The description's only added detail is the content of the payload (page address and public email), and with an output schema present even that is largely redundant. It does not contradict the annotations, but it contributes little behavioral context beyond them.

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 short sentence that front-loads the action and enumerates exactly the two returned items. Every word earns its place, with no filler or repetitive framing.

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 tool with full annotations and a declared output schema, the description supplies enough to call it correctly and to know what comes back. Nothing essential is missing, though a brief note on when this is preferable to other Virtech lookups would make it complete.

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 per the rubric the baseline is 4. There is nothing for the description to disambiguate on the input side, and the empty schema with additionalProperties=false is self-explanatory.

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 names a specific verb ('Restituisce') and two concrete resources: the Contact Us page URL and Virtech's public email. That is clearly distinct from the sibling tools get_virtech_product and list_virtech_products, though the description never explicitly contrasts itself with them, which keeps it at 4 rather than 5.

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?

No explicit when-to-use or when-not-to-use guidance is given. For a zero-parameter contact-lookup tool the intended use is strongly implied by the name and description, so it clears the minimum-viable bar, but an agent gets no stated routing rule (for example, 'use when the user asks how to reach Virtech').

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