GrowSurf

Generate REST API Library Snippets

growsurf_api_library_snippets

Read-onlyIdempotent

Generate Markdown code examples for the official backend REST API libraries in TypeScript, Python, PHP, Ruby, and Java. Select language and workflow; both default to all. Covers setup, program lookup, participant creation, referral credit, sales, and mobile participant tokens. Returns code without executing API calls. Use growsurf_client_snippets for browser JavaScript or growsurf_mobile_sdk_guide for native or React Native app setup.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "growsurf_api_library_snippets"
  }
}

Input Schema

Name	Required	Default
`email`	No
`language`	No	all
`workflow`	No	all
`campaignId`	No
`referredBy`	No
`participantIdOrEmail`	No

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 8, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare the full safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), so the bar is lower. The description usefully adds that it returns code without executing API calls, clarifying this is pure generation, but offers nothing on output shape or limits.

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?

Front-loaded with purpose, then selection parameters, coverage, the no-execution constraint, and finally sibling routing. Four sentences with no padding; each adds distinct information.

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?

An output schema exists, so return values need no explanation, and annotations cover the safety profile. The only real gap is the four context parameters (email, campaignId, referredBy, participantIdOrEmail) that an agent gets no guidance on anywhere.

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 description coverage is 0%, so the description must carry the load. It explains `language`, `workflow`, their `all` defaults, and what the workflow values cover, but leaves `email`, `campaignId`, `referredBy`, and `participantIdOrEmail` entirely undocumented in both schema and description.

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?

Specific verb (Generate) plus resource (Markdown code examples for official backend REST API libraries) with the target languages enumerated. It clearly separates itself from snippet-producing siblings by naming backend REST libraries versus browser/native SDKs.

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

Usage Guidelines5/5

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

Gives explicit routing conditions: use `growsurf_client_snippets` for browser JavaScript and `growsurf_mobile_sdk_guide` for native/React Native setup. It also states the tool returns code without executing API calls, so there is no ambiguity about side effects.

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

All GrowSurf tools Inspect

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.