List clariBI subscription tiers with prices, AI credits, data source limits, user limits, and headline features. No authentication required.
| Name | Required | Description | Default |
|---|---|---|---|
| tier | No | Optional. Return only this tier (free, trial, lite, starter, professional, enterprise). |
| Name | Required | Description | Default |
|---|---|---|---|
| tiers | Yes | ||
| currency | Yes | ISO currency code, always "USD". | |
| billing_url | Yes |
Changes observed during successful MCP inspections.
Output schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "billing_url": {
+ "format": "uri",
+ "type": "string"
+ },
+ "currency": {
+ "description": "ISO currency code, always \"USD\".",
+ "type": "string"
+ },
+ "tiers": {
+ "items": {
+ "properties": {
+ "ai_credits": {
+ "type": "integer"
+ },
+ "data_sources": {
+ "type": "integer"
+ },
+ "duration_days": {
+ "description": "Trial length in days; 0 for paid tiers.",
+ "type": "integer"
+ },
+ "headline_features": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "id": {
+ "type": "string"
+ },
+ "max_users": {
+ "type": "integer"
+ },
+ "name": {
+ "description": "Display name of the tier.",
+ "type": "string"
+ },
+ "price_monthly_usd": {
+ "type": "number"
+ },
+ "price_yearly_usd": {
+ "type": "number"
+ },
+ "storage_gb": {
+ "type": "number"
+ }
+ },
+ "required": [
+ "id",
+ "name",
+ "price_monthly_usd",
+ "price_yearly_usd"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ }
+ },
+ "required": [
+ "currency",
+ "tiers",
+ "billing_url"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safe read-only nature. The description adds valuable behavioral context by explicitly stating 'No authentication required' and enumerating the specific data fields returned. It does not contradict the annotations and provides additional operational detail.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise, consisting of two short sentences. The primary action and resource are front-loaded, and every phrase adds useful detail (what is listed, and the auth requirement). No redundant or filler content.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple tool with one optional parameter, full schema coverage, an output schema, and comprehensive annotations, the description provides all necessary context: what it does, what it returns, and the lack of auth requirement. Nothing critical is omitted.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema already fully describes the only parameter (tier) with its allowed values, providing 100% coverage. The description adds no extra meaning beyond what the schema offers, so the baseline of 3 is appropriate given the high schema coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's function with a specific verb ('List') and resource ('clariBI subscription tiers'), detailing exactly what is returned (prices, AI credits, data source limits, user limits, headline features). It is easily distinguishable from sibling tools like get_billing_status or create_checkout_session, which focus on billing status or checkout flows.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear context for when to use the tool by specifying that it lists subscription tiers and pricing, and explicitly notes that no authentication is required. While it does not explicitly name alternatives or exclusion cases, the context is sufficient for an agent to select it correctly among siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.