Skip to main content
Glama
growsurf

GrowSurf MCP Server

Official
by growsurf
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

growsurf_grsf_config_snippet

Read-onlyIdempotent

Generate the head snippet for participant auto-auth using 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
NameRequiredDescriptionDefault
hashNo
emailNo
campaignIdNo
affiliateJoinNo
useCampaignIdPlaceholderNo
enableParticipantAutoAuthNo
includeAutoAuthCommentHeaderNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
markdownNoThe generated guidance as a markdown document.

Tool Definition Quality

A3.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, so the description doesn't need to cover safety. It adds value by specifying the output artifact (a code snippet) and the configuration context (participant auto-auth, window.grsfConfig), which are not in annotations. No contradiction.

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?

One sentence with zero redundancy; the primary purpose and placement are front-loaded. Everything present earns its place.

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?

Despite having an output schema, the tool description omits essential details about parameter usage and selection logic. With 7 undocumented parameters and multiple sibling snippet tools, the description is insufficient for an agent to confidently invoke this tool correctly.

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?

Schema description coverage is 0% and the tool description provides no parameter explanations. With 7 optional parameters (hash, email, campaignId, affiliateJoin, etc.), the agent has no guidance on what values to provide or how they affect the snippet. The description fails 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 clearly states the tool generates a <head> snippet for participant auto-auth using window.grsfConfig, with a specific placement instruction. This distinguishes it from other snippet tools like growsurf_embeddable_element_snippet or growsurf_client_snippets by naming the purpose (auto-auth) and the configuration variable.

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 provides a placement instruction ('place before the GrowSurf Universal Code') but does not explain when to choose this tool over other snippet-related siblings. Given the large set of sibling tools, an agent would benefit from explicit selection criteria, which are absent.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/growsurf/growsurf-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server