Skip to main content
Glama

Bernuvia

by com.bernuvia
OverviewDiscussionsAdmin

my_referral_code

Returns your referral code and link with their stats (when the programme is active).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeNoThe @handle, which is the referral code.
linkNoLink with `?ref=` to share.
activeYesThe referral program is active.
messageNoOnly with `active: false`: why there is nothing to give.
paidUsdcNoCommission already paid, in USDC.
referredNoHow many people signed up with the link.
pendingUsdcNoCommission accrued and unpaid, in USDC.
activeReferredNoOf those, how many have already generated some commission.
buyCommissionPctNoPercentage OF THE COMMISSION for the referred user's purchases.
sellCommissionPctNoPercentage OF THE COMMISSION for the referred user's sales.
freeMonthsForReferredNoFree months that whoever signs up gets.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changed
    • changedOutput schema / properties / active / description
      Previous value: -"El programa de referidos está activo."New value: +"The referral program is active."
    • changedOutput schema / properties / activeReferred / description
      Previous value: -"De esas, cuántas ya generaron alguna comisión."New value: +"Of those, how many have already generated some commission."
    • changedOutput schema / properties / buyCommissionPct / description
      Previous value: -"Porcentaje DE LA COMISIÓN por las compras del referido."New value: +"Percentage OF THE COMMISSION for the referred user's purchases."
    • changedOutput schema / properties / code / description
      Previous value: -"El @handle, que es el código de referido."New value: +"The @handle, which is the referral code."
    • changedOutput schema / properties / freeMonthsForReferred / description
      Previous value: -"Meses gratis que se lleva quien se registra."New value: +"Free months that whoever signs up gets."
    • changedOutput schema / properties / link / description
      Previous value: -"Enlace con `?ref=` para compartir."New value: +"Link with `?ref=` to share."
    • changedOutput schema / properties / message / description
      Previous value: -"Solo con `active: false`: por qué no hay nada que dar."New value: +"Only with `active: false`: why there is nothing to give."
    • changedOutput schema / properties / paidUsdc / description
      Previous value: -"Comisión ya pagada, en USDC."New value: +"Commission already paid, in USDC."
    • changedOutput schema / properties / pendingUsdc / description
      Previous value: -"Comisión acumulada sin pagar, en USDC."New value: +"Commission accrued and unpaid, in USDC."
    • changedOutput schema / properties / referred / description
      Previous value: -"Cuántas personas se registraron con el enlace."New value: +"How many people signed up with the link."
    • changedOutput schema / properties / sellCommissionPct / description
      Previous value: -"Porcentaje DE LA COMISIÓN por las ventas del referido."New value: +"Percentage OF THE COMMISSION for the referred user's sales."
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does reveal that the tool returns a code, a link, and stats, and that this occurs only when the programme is active. However, it does not explain what happens when the programme is inactive, whether authentication is required, or whether the returned link is ever missing or null. This is a partial but not complete behavioral picture.

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?

The description is a single, efficient sentence that front-loads the return resource and includes the only relevant conditional qualifier. Every word contributes meaning, and there is no unnecessary repetition or filler.

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 zero-parameter, simple read-style tool with an output schema present, the description is largely complete: it names what is returned and includes the key activation condition. The main omission is the behavior when the programme is inactive, but given the tool's low complexity and the presence of an output schema, this is a minor gap rather than a fatal one.

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?

The tool has zero parameters, and the schema coverage is trivially 100%. The baseline for no-parameter tools is 4, and the description adds nothing about parameters because none exist. No parameter documentation is needed here.

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 states a specific verb ('Returns'), a clear resource ('your referral code and link'), and an additional output detail ('with their stats'). It also adds the condition 'when the programme is active,' which distinguishes this tool's behavior from a generic referral lookup and makes its purpose unmistakable.

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

Usage Guidelines2/5

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

The description gives no explicit guidance on when to use this tool versus alternatives, and provides no exclusions beyond the vague note about the programme being active. Since the tool has no direct sibling named similarly, the description could have clarified the intended scenario, such as retrieving the caller's own referral details, but it leaves that to inference.

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

All Bernuvia toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources