Skip to main content
Glama

ProfBlu

ProfBlu pricing

get_pricing
Read-onlyIdempotent

Today's plans and prices of Brod and Cassa, read live from ProfBlu's billing: monthly and yearly price, people (and properties) included, price of each extra one, free trial, in EUR and, where it exists, the Latin America plan in USD. Prices exclude VAT. 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": "get_pricing"
  }
}

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
productNoOnly this product (brod or cassa). Without it, both.

Output Schema

NameRequiredDescriptionDefault
langYes
plansYes
vatNoteYes
pricingUrlYesThe pricing page on profblu.com: cite it

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 genuinely useful context beyond them: the data is read live from billing, prices exclude VAT, EUR is the base currency with a conditional USD Latin America plan, and free trial information is included. It stops short of auth or rate-limit details, which keeps it at a 4.

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 dense sentence that front-loads the resource and then lists the returned fields, with no filler. It is slightly run-on and the parenthetical '(and properties)' interrupts flow, but nearly every clause carries 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 values need no explanation, and the description already covers currency, VAT exclusion, trial information, and language handling. An agent has everything needed to invoke it correctly; only explicit sibling routing is missing.

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 coverage is 100%, so both parameters are already documented in the schema, establishing the baseline of 3. The description adds only marginal meaning: it confirms answers come back in the requested lang, and naming 'Brod and Cassa' implicitly explains that omitting product returns both.

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 ('plans and prices ... read live from ProfBlu's billing') and enumerates the exact fields returned (monthly/yearly price, seats included, extra-seat price, free trial, currencies). This is clearly distinguishable from siblings like list_products, which would give catalog data rather than 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: the agent can infer this is the tool for pricing questions, but there is no explicit when-to-use guidance, no named alternatives, and no statement of when not to call it. There is a hint that data is live, which discourages caching assumptions, but that is not routing guidance.

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