Skip to main content
Glama

Profilo di OpenMind

Profilo del prodotto

get_product_profile
Read-onlyIdempotent

Legge il profilo pubblico di OpenMind, con descrizione, destinatari, funzionalità e link ufficiali.

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_product_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
demoYes
productYes
publisherYes
resourcesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

While annotations cover safety (read-only), the description adds valuable behavioral context by specifying that it retrieves *public* data and enumerates the types of information returned (e.g., audiences, features). This helps the agent understand the nature of the output.

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?

The definition is presented as a single, concise sentence that immediately identifies the tool's function without any fluff or unnecessary elaboration.

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?

Given the low complexity (zero input parameters) and the clear definition of the data scope, the definition is highly complete. It provides all necessary context for the agent to safely and accurately invoke the tool.

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 input schema has zero parameters, so the description does not need to explain specific field semantics. The description correctly focuses on the overall scope of the information retrieved.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a precise verb ('Legge il profilo') and specifies the content returned, including description, audiences, features, and official links, making the purpose unambiguous and distinct from other product tools.

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 description clearly defines the scope (public profile summary), but it does not explicitly state when to use it versus alternative tools like 'find_product_resources.' Usage context is implied by the content retrieved.

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