Cello

cello_get_program_metrics

Read-only

Get complete referral program metrics in one call: lifetime totals, weekly and monthly history, and industry benchmarks. Use for questions about program performance, stats, trends, revenue, funnel metrics, or industry comparisons.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`currency`	Yes	ISO currency code for all monetary values (e.g. EUR, USD)
`benchmarks`	No	Industry benchmarks by GTM motion plus the customer's own rates
`historyByWeek`	No	Weekly time series; 'periods' contains complete weeks only, 'latestPeriod' is the current week
`allTimeMetrics`	No	Lifetime cumulative totals plus recent monthly/weekly changes
`historyByMonth`	No	Monthly time series; 'periods' contains complete months only, 'latestPeriod' is the current month

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. Description adds what metrics are included (lifetime totals, weekly/monthly history, benchmarks), providing additional context beyond annotations.

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

Conciseness5/5

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

Two sentences, front-loaded with main action, no wasted words. Structure is efficient and clear.

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 zero parameters and output schema present, description adequately covers purpose and usage. Could be improved by mentioning data freshness or update frequency, but overall sufficient for a simple metrics tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

No parameters; schema coverage is 100%. Baseline score of 4 is appropriate as description explains tool's return content without needing param details.

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?

Clear verb 'Get' with specific resource 'complete referral program metrics' and details includes lifetime totals, weekly/monthly history, benchmarks. Distinct from sibling tools like get_events, get_referrers, etc.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use: 'for questions about program performance, stats, trends, revenue, funnel metrics, or industry comparisons.' No explicit when-not or alternatives, but context is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Cello tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0

Disambiguation5/5

Each tool targets a distinct aspect of the Cello platform: events, integration status, metrics, recommendations, referrers (general and top), and documentation search. No two tools have overlapping purposes; descriptions clearly differentiate them.

Naming Consistency5/5

All tools follow a consistent pattern with 'cello' prefix, verb (get or search), and snake_case noun. The verb choice is appropriate for each operation, and the naming is predictable and uniform.

Tool Count5/5

With 7 tools, the set is well-scoped for a referral program analytics and diagnostics server. Each tool fills a necessary role without being excessive or too sparse.

Completeness4/5

The tool set covers all key read-only diagnostics: events, integration health, metrics, recommendations, referrers, and documentation. However, it lacks any write or configuration tools, which may be expected for a comprehensive integration server, but the surface is complete for its apparent diagnostic purpose.

Resources

Need Help?