Skip to main content
Glama

ProfBlu

ProfBlu products

list_products
Read-onlyIdempotent

Lists the software products ProfBlu sells to small businesses (Brod for gyms and personal trainers, Cassa for holiday rental agencies): who each one is for, what it solves, today's starting price, its website and the canonical url of its page on profblu.com. Answers in the language requested with lang (es, en, it).

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": "list_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the answer: es (Spanish), en (English) or it (Italian). Defaults to en. Use the language the user writes in.en

Output Schema

NameRequiredDescriptionDefault
langYes
productsYes
pricingUrlYesThe pricing page on profblu.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds value beyond them by disclosing the shape of the returned catalog (target audience, problem solved, current starting price, website, canonical URL) and flagging that price is "today's" — a freshness signal worth noting. Auth, rate limits and pagination are not mentioned, but neither is required for a small static catalog.

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?

One sentence, front-loaded with the purpose, then a colon-introduced list of returned fields and a closing note on language. Dense but every clause carries information; the parenthetical product descriptions are the only part that could arguably be trimmed.

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?

With an output schema present, return values need not be spelled out, yet the description still summarizes them helpfully, and it covers scope, language behavior and price freshness for a one-optional-parameter read tool. The only gap is the absence of any disambiguation from get_pricing, which an agent may otherwise confuse with this tool.

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% and the single lang parameter is fully enumerated with a default, so the schema already does the work. The description's "Answers in the language requested with lang (es, en, it)" restates the schema rather than adding meaning such as fallback behavior for unsupported languages. Baseline 3 applies.

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?

States a specific verb and resource ("Lists the software products ProfBlu sells") and goes further by naming the two products and their target markets (Brod for gyms, Cassa for holiday rentals). It also enumerates what each entry contains, so an agent knows exactly what a call yields without opening the schema.

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: an agent infers this is the catalog tool for product questions. There is no explicit when-to-use, no when-not-to-use, and no routing against the siblings list_websites, get_pricing or how_to_start, despite the overlap in coverage of "today's starting price" with get_pricing.

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