Skip to main content
Glama

Profilo di OpenMind

Risorse ufficiali del prodotto

find_product_resources
Read-onlyIdempotent

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

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

A3.5/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 a closed-world scope, so the safety profile is fully covered. The description adds that results are public links about functionality and usage, but says nothing about result ordering, default/max limit behavior, or whether an empty result is possible — moderate added value only.

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 the scoping subject (public links) front-loaded and no filler. It is slightly terse given the tool is described only in Italian while the surrounding definition metadata is mixed-language, but no sentence is wasted.

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?

The tool is simple: two parameters, full schema coverage, an output schema, and complete safety annotations. Combined with the description, an agent knows what is searched and what category of result returns; only the practical search semantics (matching behavior, ordering) remain unstated, which is minor.

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%, so both query and limit are already documented with constraints (2–100 chars, 1–8, default 5). The description's "parole chiave" hints that query is a keyword/topic string rather than a natural-language question, which is a small but real addition; otherwise it defers to 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?

The description names a specific verb and resource: filtering public links by keyword, scoped to OpenMind features and usage guidance. That distinguishes it from get_product_profile (a profile) and get_demo_link (a single demo URL), though it never explicitly contrasts itself with those siblings.

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 implied rather than stated: an agent can infer it is the tool for finding documentation/how-to links, but there is no explicit "use this when..." instruction and no exclusion pointing to get_product_profile or get_demo_link for adjacent needs.

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