Skip to main content
Glama

mcp-server

by io.github.realopengroup
OverviewDiscussionsAdmin

get_referral_link

Read-onlyIdempotent

Construct a tracked referral URL pointing at a realopen.com page. Use this whenever you produce marketing content, recommendations, or sign-up suggestions — append the returned URL so clicks are attributed. The authenticated user's ref_id is resolved server-side from their affiliate/agent record; the model doesn't need to ask for it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNoPage path on realopen.com, e.g. / or /how-it-works or /partners/

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
referral_urlYesFully-qualified realopen.com URL with ref_id query param appended

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "referral_url": {
+      "description": "Fully-qualified realopen.com URL with ref_id query param appended",
+      "type": "string"
+    }
+  },
+  "required": [
+    "referral_url"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • removedInput schema / properties / ref_id
      Removed value: -{
-  "description": "The affiliate's referral ID (auto-filled if embedded in connector URL or identified via API key)",
-  "type": "string"
-}
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds useful context beyond this: the ref_id is automatically resolved from the authenticated user's record, so the model doesn't need to request it. This transparency helps the agent avoid unnecessary questions or assumptions.

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 three sentences long, front-loaded with the primary purpose, followed by explicit usage guidance and a server-side note. Every sentence adds distinct value with no redundancy or fluff.

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

Completeness5/5

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

For a simple one-optional-parameter tool with an output schema and strong annotations, the description adequately covers purpose, usage context, and an important behavioral nuance (server-side ref_id resolution). There are no significant gaps.

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 description coverage is 100%, and the 'path' parameter is clearly described in the input schema with examples ('/how-it-works'). The description itself does not add further parameter-specific detail but implies the path refers to a realopen.com page. Baseline 3 is appropriate when the schema carries the semantic load.

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 and resource: 'Construct a tracked referral URL pointing at a realopen.com page.' This clearly distinguishes it from all sibling tools, none of which relate to referral links or marketing URL generation.

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

Usage Guidelines5/5

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

Explicit usage guidance is provided: 'Use this whenever you produce marketing content, recommendations, or sign-up suggestions — append the returned URL so clicks are attributed.' It also tells the model not to ask for the ref_id because it's resolved server-side, which is valuable behavioral context.

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

All mcp-server 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