Skip to main content
Glama

Referral Generation Forecast

bpj_referral_generation_forecast
Read-onlyIdempotent

Project referral generations from invitations and activation probability, assuming distinct recipients and no audience saturation.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "seed": "<seed>",
      "invitations": "<invitations>",
      "activation": "<activation>",
      "generations": "<generations>"
    },
    "name": "bpj_referral_generation_forecast"
  }
}

Input Schema

NameRequiredDescriptionDefault
seedYes
activationYes
generationsYes
invitationsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so safety is fully covered by structured data. The description does earn credit for disclosing the model's core assumption ('distinct recipients and no audience saturation'), which tells the agent the output is an upper-bound projection and will overstate results in saturated audiences. It stops short of describing output shape or rounding.

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 tight sentence with no filler, and the modeling assumption is appended where it is most useful. It is perhaps too compact given four undocumented parameters, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only projection with no output schema, the description should say what the result contains (total referrals? per-generation breakdown?), which it omits. The assumptions disclosure partially compensates, but an agent cannot predict the return value or the effect of the 12-generation cap.

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

Parameters2/5

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

Schema description coverage is 0%, so the description carries the full burden, and it only loosely echoes three of the four inputs. It never clarifies that 'generations' means the number of referral rounds (capped at 12) versus 'seed' as the initial referring-user count, and it does not explain that 'invitations' is a per-new-user rate. The critical distinction between seed users and per-generation counts is left to the agent.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource: 'Project referral generations from invitations and activation probability.' An agent immediately knows this is a forward-looking model rather than a lookup or mutation, though it does not name any sibling forecast to distinguish itself from the many other bpj_*_forecast tools.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no alternatives are named. The reader must infer from the word 'Project' that this is a modeling/simulation call rather than a data retrieval call; nothing states prerequisites such as needing a starting user base.

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.