GrowSurf MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

growsurf_troubleshoot_referral_tracking

Read-onlyIdempotent

Diagnose referral tracking problems: returns ordered checks, likely causes, fixes, and doc links for uncredited referrals, missing participant emails, unrewarded referrals, and integration sync issues.

Instructions

Call first for a program problem, even without a program or participant ID. It returns initial checks; ask for IDs before reading records. Covers referrals not credited, participant emails not sending, rewards not issued, participants not added, Universal Code not detected, an integration or CRM (HubSpot, Mailchimp, and others) not syncing, Zapier errors, fraud flags, analytics numbers that look wrong, and more. Returns the checks to run in order (with the read tool and field for each), the likely causes most common first, fixes, and doc links. Pass a symptom key; unknown keys return the available symptoms; a description is matched only when it contains a symptom's label or alias verbatim, otherwise the symptom list is returned.

Input Schema

TableJSON Schema

Name	Required	Description
`symptom`	No	The symptom to diagnose. Known keys: `participant_emails_not_sending`, `reward_not_issued`, `referral_not_credited`, `participants_not_added`, `universal_code_not_detected`, `platform_specific_install`, `numbers_do_not_match`. Unknown keys return the symptom list.
`campaignId`	No	Target program (campaign) id for this call. Defaults to GROWSURF_CAMPAIGN_ID when omitted. Pass the `id` returned by growsurf_create_campaign to configure or operate a program you just created, without restarting the server.
`description`	No	The problem in the customer's words, when `symptom` is unknown.
`participantId`	No	Affected participant id, echoed into participant-level checks.
`participantEmail`	No	Affected participant email, when the id is unknown.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`markdown`	No	The generated guidance as a markdown document.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.14.0Sep 10, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds behavioral context: it returns checks to run, likely causes, fixes, and doc links. It also explains the matching behavior for the description parameter. This goes beyond the annotations without contradicting them.

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?

The description is dense but front-loaded with the most important instruction ('Call first') and then systematically lists coverage, return content, and parameter behavior. Every sentence adds value, though it is somewhat long; still, no 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?

Given the tool's complexity (multiple symptoms, optional parameters, output schema), the description is fully complete: it explains what the tool returns, how to supply input, how matching works, and the need to ask for IDs. It covers all the context an agent needs to invoke it correctly.

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?

All five parameters have schema descriptions (100% coverage), and the description adds meaning beyond the schema: it explains the symptom key behavior, the campaignId default, and how description matching works. This enriches the schema's baseline of 3.

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 ('troubleshoot') and resource ('referral tracking'), then enumerates the exact problem categories it covers, making it unmistakable what the tool does. It clearly distinguishes itself from sibling tools by being the diagnostic entry point.

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?

The description explicitly instructs to call this tool first for any program problem and explains when to pass a symptom vs a description, and how unknown keys behave. It doesn't name alternative tools or explicitly say when not to use it, but the 'call first' directive is a strong usage rule.

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

Deploy Server