Skip to main content
Glama

Catalogo prodotti Virtech

Scheda di un prodotto Virtech

get_virtech_product
Read-onlyIdempotent

Trova il prodotto attraverso il suo identificativo esatto, per esempio tracciamy.

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": {
      "id": "<id>"
    },
    "name": "get_virtech_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Output Schema

NameRequiredDescriptionDefault
productYes

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 readOnlyHint=true, idempotentHint=true, destructiveHint=false and closed-world, so the safety profile is fully covered structurally. The description adds only the exact-match requirement and says nothing about what happens on a miss or how the lookup behaves; no contradiction with annotations.

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?

A single front-loaded sentence with no filler, and the identifying constraint comes before the example. It is efficient but borders on under-specification for a tool whose sibling relationship is ambiguous.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (one required param, output schema present so return values need no explanation), which lowers the bar. Still, the description omits the not-found behavior and any contrast with list_virtech_products, which an agent would need to route 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?

Schema description coverage is 0%, so the description must carry the meaning, and it does add value: 'esatto' clarifies exact rather than partial matching, and the sample value 'tracciamy' illustrates the lowercase slug format that the schema's regex pattern encodes. It still never names the parameter or states case sensitivity.

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 ('Trova') and resource ('prodotto') plus the lookup key ('identificativo esatto'), so an agent can tell it retrieves a single product. It does not explicitly distinguish itself from siblings like list_virtech_products, leaving the single-item vs. list split to inference from the word 'esatto'.

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 'identificativo esatto' implies this is for exact-key lookups rather than searching, which is useful context, but no alternative tool is named and there is no guidance on when not to use it or what to do when the ID is unknown. Usage is only implied.

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