Skip to main content
Glama

ProfBlu

Get started with a ProfBlu product

how_to_start
Read-onlyIdempotent

How to start with Brod or Cassa: the sign-up link for the free trial (and how long it lasts), where to sign in, the mobile app and the plans, with the canonical url of the product page on profblu.com. Answers in the language requested with lang (es, en, it).

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": {
      "product": "<product>"
    },
    "name": "how_to_start"
  }
}

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
productYesThe product: brod (gyms and personal trainers) or cassa (holiday rental agencies).

Output Schema

NameRequiredDescriptionDefault
urlYesCanonical page on profblu.com: cite it
langYes
nameYes
stepsYes
productYes
appStoreNo
loginUrlNo
signupUrlNo
trialDaysNo
pricingUrlYes

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=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds that answers are localized via lang and that a canonical profblu.com URL is included, but says nothing about response shape or coverage limits beyond the enumerated topics.

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 sentence that front-loads the two product names and then enumerates returned content; nothing is redundant. It is dense but each clause corresponds to a distinct piece of returned information.

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-value explanation is unnecessary, and both parameters are documented. For a simple two-parameter informational lookup, the description covers what an agent needs; only the relationship to get_pricing is left ambiguous.

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 both parameters carry enums with explanatory descriptions, so the schema already carries the semantic load. The description mentions lang and its three values, but adds no format or behavioral detail beyond what the enum and descriptions state.

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 the concrete content the tool returns for a given product: sign-up link, free-trial duration, sign-in location, mobile app availability, plans, and the canonical product-page URL. That is specific enough to distinguish it from a pure pricing lookup, but the mention of 'plans' overlaps with the get_pricing sibling without explaining the boundary between them.

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 enumerated content — an agent can infer this is the onboarding/FAQ tool for brod and cassa. There is no explicit statement of when to prefer it over get_pricing or list_products, and no exclusions or prerequisites are given.

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