GrowSurf MCP Server

Official

by growsurf

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

Participant Auto-Auth Snippet

growsurf_grsf_config_snippet

Read-onlyIdempotent

Generate the head snippet for participant auto-auth by setting window.grsfConfig, to be placed before the GrowSurf Universal Code.

Instructions

Generate the snippet for participant auto-auth using window.grsfConfig (place before the GrowSurf Universal Code).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`hash`	No
`email`	No
`campaignId`	No
`affiliateJoin`	No
`useCampaignIdPlaceholder`	No
`enableParticipantAutoAuth`	No
`includeAutoAuthCommentHeader`	No

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.

First observedv0.12.2Aug 25, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false), so the bar is lower. The description adds meaningful behavioral context by specifying placement in the <head> and the ordering requirement before the GrowSurf Universal Code — a non-obvious constraint that could break the integration if ignored.

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?

A single sentence with zero filler: the verb and resource are front-loaded, and the parenthetical placement instruction earns its place. There is no redundancy with the title or annotations.

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

Completeness2/5

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

For a tool with 7 parameters, 0% schema coverage, and no parameter documentation, the description is too thin. Even though an output schema exists to cover return values, an agent cannot reasonably decide how to set enableParticipantAutoAuth, affiliateJoin, useCampaignIdPlaceholder, or how the hash should be computed, making the tool under-specified for correct invocation.

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

Parameters1/5

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

With 0% schema description coverage and 7 parameters, the description carries the full burden of explaining parameters, but it mentions none of them — hash, email, campaignId, affiliateJoin, useCampaignIdPlaceholder, enableParticipantAutoAuth, and includeAutoAuthCommentHeader are all undocumented. The description does nothing to compensate for the schema gap.

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 uses a specific verb ('Generate') with a concrete resource (the <head> snippet for participant auto-auth) and states the exact mechanism (window.grsfConfig). It also gives installation context ('place before the GrowSurf Universal Code'), making it clearly distinguishable from siblings like growsurf_client_snippets or growsurf_embeddable_element_snippet.

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

Usage Guidelines3/5

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

The description implies the use case by naming participant auto-auth and the placement constraint relative to the Universal Code, which gives the agent situational context. However, it never explicitly contrasts this tool with alternatives (e.g., when to use this vs. growsurf_client_snippets or growsurf_participant_auth_hash) and provides no exclusions.

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

Deploy Server