Skip to main content
Glama

Profilo di Appuntamy

Risorse ufficiali del prodotto

find_product_resources
Read-onlyIdempotent

Filtra per parole chiave i collegamenti pubblici sulle funzionalità e su come usare Appuntamy.

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.4/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 covered. The description adds that results are public links about product features and usage, which is useful context, but says nothing about result volume limits, language, or ranking behavior.

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 well-formed sentence with no wasted wording and the search intent front-loaded. It is efficient, though its brevity leaves little room for guidance.

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?

With a full parameter schema, an output schema, and rich annotations, the description need not explain returns or safety. It is minimally sufficient, but for a search tool it omits what the returned resources cover and how to scope a query, leaving gaps for an agent choosing among siblings.

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%, including the limit default of 5 and the query length bounds, so the schema already carries parameter meaning. The description only restates that filtering is by keyword, adding no syntax or matching semantics 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 specific verb plus resource: 'Filtra per parole chiave i collegamenti pubblici' scoped to features and how to use Appuntamy. An agent knows this is a keyword search over public documentation links, though the distinction from siblings like get_product_profile rests on inference rather than explicit contrast.

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 by the keyword-filter phrasing; there is no explicit statement of when to prefer this over get_product_profile or get_demo_link, nor any exclusion of cases where it should not be used.

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