Skip to main content
Glama

ProfBlu

ProfBlu websites

list_websites
Read-onlyIdempotent

Lists the free public websites ProfBlu publishes —Prim (Argentine streaming audiences), Siami (snow, ski, kite, diving and surf spots), Muchmer (theatre and cinema listings), Pelusa (football), Pucará (Argentine Olympic sport), Milésima (Formula 1 data), Argento (Argentine businesses abroad) and La lonja (sports schools and shops)— with what each one offers, its latest figures, its url, the canonical url of its page on profblu.com and its own MCP server when it has one. 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_websites"
  }
}

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
websitesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorldHint=false, so safety is covered. The description adds that the sites are free and public and that each entry carries figures, URLs and an MCP server reference, but says nothing about ordering, pagination or freshness beyond 'latest figures'.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening clause is well front-loaded, but the nine-site parenthetical enumeration dominates the text and largely duplicates what the output schema likely already returns. It earns some routing value (e.g. an agent can spot 'Formula 1' maps to Milésima) but is wordier than needed.

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?

For a zero-required-parameter, read-only listing tool with full annotations and an output schema, this is complete: purpose, returned fields and language behavior are all covered. Only explicit sibling routing is absent.

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 already documents es/en/it with a default of en. The description restates the same enum and adds only the mild hint that the answer follows the requested language; 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?

Specific verb plus resource plus scope: 'Lists the free public websites ProfBlu publishes', then names each site and what it covers. An agent can immediately tell this is the brand/site catalog tool and not list_products or get_pricing.

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 can infer this is the discovery tool for ProfBlu's properties, but the description never states when to choose it over siblings like list_products or how_to_start, nor any preconditions.

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