Skip to main content
Glama
Sign In

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

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

Output 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
    • removedInput schema / additionalProperties
      Removed value: -false
  2. 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"
+}
  3. 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"
-}
  4. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely non-obvious context: the ref_id is resolved server-side from the affiliate/agent record and must not be requested from the user, and the returned URL must be appended for click attribution. It doesn't discuss failure behavior when no affiliate record exists, which would have made it a 5.

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?

Three tight sentences: what it does, when to use it, and the key implementation caveat. Nothing is redundant and the most decision-relevant information (the action) is front-loaded.

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 an output schema present, return values need not be explained, and the description covers purpose, usage, and the ref_id resolution behavior. The only omission is what happens when the user has no affiliate record, which leaves a small edge-case gap.

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 'path' parameter is documented with examples and a default, so the description adds little parameter detail beyond the domain hint 'realopen.com page.' Baseline 3 is appropriate when the schema carries the semantics.

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?

States a specific verb and resource — 'Construct a tracked referral URL' pointing at a realopen.com page — which is unambiguous and clearly distinct from every sibling tool listed (wallet, status, and content tools). An agent knows exactly what artifact this produces.

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?

Gives an explicit trigger set: 'whenever you produce marketing content, recommendations, or sign-up suggestions.' That is strong positive guidance. It stops short of naming when-not-to-use cases or alternatives, but no sibling overlaps this function, so the gap is minor.

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