@thryx/mcp-server

thryx_set_referrer

Set a referrer wallet for your account to reward the referrer with 5% of protocol fees on every trade.

Instructions

Set a referrer wallet for your account. The referrer earns 5% of the protocol fee share on every trade you make.

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": {
      "referrer": "<referrer>"
    },
    "name": "thryx_set_referrer"
  }
}

Input Schema

Name	Required	Description	Default
`referrer`	Yes	Referrer wallet — 0x-prefixed 40-char hex.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.5.0Aug 4, 2026

TDQS

B3.3/5.0

Behavior3/5

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It does reveal a key consequence (the referrer earns 5% of protocol fee share), which adds useful context. However, it doesn't disclose whether the operation is reversible, requires specific permissions, or has side effects beyond the fee share, leaving gaps.

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?

Two sentences with zero filler. The description is front-loaded with the action and immediately provides a relevant consequence. Every word earns its place.

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 simple single-parameter tool, the description covers the core purpose and a consequence, but it lacks usage guidance and doesn't clarify how this relates to sibling tools like thryx_claim_referral. Without annotations or an output schema, more contextual detail would improve completeness.

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% with a clear description for the referrer parameter ('0x-prefixed 40-char hex'). The tool description adds context that the referrer earns fees, which helps explain the parameter's role, but it doesn't elaborate on format or constraints beyond the schema. This matches the baseline for high schema coverage.

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 clearly states the action: 'Set a referrer wallet for your account.' This is a specific verb+resource combination. It doesn't explicitly differentiate from siblings like thryx_claim_referral, but the action is distinct enough that a capable agent would understand the purpose.

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 provides no guidance on when to use this tool vs alternatives. It doesn't mention prerequisites, exclusions, or call out related tools like thryx_claim_referral. This leaves the agent to infer usage context on its own.

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