Skip to main content
Glama

Profilo di Tracciamy

Risorse ufficiali del prodotto

find_product_resources
Read-onlyIdempotent

Filtra per parole chiave i collegamenti pubblici sulle funzionalità e su come usare 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": {
      "query": "<query>"
    },
    "name": "find_product_resources"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumero massimo di risorse. Il valore predefinito è 5.
queryYesArgomento da cercare tra le risorse ufficiali

Output Schema

NameRequiredDescriptionDefault
resourcesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description's only added behavioral signal is that resources are 'pubblici' and 'ufficiali', i.e. no private or user-generated content is searched — useful but thin, with nothing on limits or ranking.

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 compact sentence with no filler and the key scope words front-loaded. It is efficient, though it leaves no room for the clarifying detail the tool would benefit from.

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?

An output schema exists, annotations are rich, and both parameters are fully documented in-schema, so the description only needs to frame scope — which it does. A brief note on when to prefer this over the sibling tools is the main missing piece.

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 description coverage is 100%, with both query and limit documented in-schema (min/max length, default 5, max 8), so the baseline is 3. The description only reinforces that filtering is keyword-based over official resources and adds no syntax or matching details 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?

States a concrete verb plus resource: keyword filtering of public links about features and how to use Tracciamy. This is clearly narrower than get_product_profile or get_demo_link, but the description never names those siblings, so the agent must infer the separation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not guidance and no reference to the sibling tools. At best the phrase 'parole chiave' implies a keyword search over official documentation, which the agent has to infer unaided.

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