Skip to main content
Glama

Get my referral stats

getReferralStats
Read-onlyIdempotent

The candidate's Referral page: their personal share link, how many people they invited and how many signed up in the window, how many visited the link, and the most recent referrals by name. The share link is the thing to hand over when they want to refer someone; it is theirs and safe to send.

Clera privately records this tool's inputs and results for usage tracking and support.

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": "getReferralStats"
  }
}

Input Schema

NameRequiredDescriptionDefault
windowDaysNoCount the last 30 or 90 days.

Output Schema

NameRequiredDescriptionDefault
recentYes
invitedYes
signedUpYes
shareLinkYes
windowDaysYes
pageVisitorsYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish this as a read-only, idempotent, closed-world call, so the safety profile is covered. The description adds value beyond that by stating the data is the candidate's own, that the share link is safe to send on, and that Clera records inputs and results for usage tracking and support — a disclosure the annotations do not carry. It stops short of noting anything about freshness or scope of the 'most recent referrals' list.

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?

It is front-loaded with the resource and its contents, then follows with the practical share-link guidance. The telemetry sentence is boilerplate-adjacent but does convey new information; the middle sentence is slightly dense with comma-separated data points but stays readable.

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 one-optional-parameter, read-only tool with an output schema, this describes the payload shape well enough that the agent knows what to expect without relying on the schema alone. Nothing critical to correct invocation is missing; only time-window behavior (e.g., what happens with no recent referrals) is left unstated.

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% and the single windowDays parameter already documents the 30/90-day options and the default. The description only alludes to it via 'in the window,' adding no format or edge-case meaning, so the 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?

The description names a specific resource (the candidate's Referral page) and enumerates exactly what comes back: personal share link, invite count, signup count within the window, link visits, and recent referrals by name. That level of detail clearly separates it from sibling 'get' tools like getProfileStrength or getDashboardLink.

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?

There is one concrete usage cue: the share link is 'the thing to hand over when they want to refer someone,' which tells the agent when the output is actionable. However, it gives no when-not guidance and does not point to any alternative tool or condition, so the routing guidance is only implied.

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