Skip to main content
Glama
GrowSurf MCP Server

GrowSurf MCP Server

Official

Get Mobile SDK Guide

growsurf_mobile_sdk_guide
Read-onlyIdempotent

Get Markdown guidance for integrating native iOS/Android or React Native GrowSurf SDKs, including attribution, share links, share tracking, and tailored setup for participant states.

Instructions

Get Markdown implementation guidance for native iOS/Android SDK 0.10.6 or React Native SDK 0.3.4, including attribution, shareUrl sharing, trackShare, and the native GrowSurf Window. Choose platform and participantState to tailor the guide; includeInstallSnippets controls installation examples. Does not install an SDK or create a participant token. Use growsurf_client_snippets for browser JavaScript or growsurf_api_library_snippets for backend token-creation code.

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_mobile_sdk_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
platformNo`both` renders the native iOS and Android SDKs. `react_native` renders the React Native SDK for bare React Native apps and Expo development builds.both
campaignIdNo
mobilePublicKeyNo
participantStateNoboth
attributionProviderNoall
includeInstallSnippetsNo
serverVerifiedQualifyingActionNo

Output Schema

NameRequiredDescriptionDefault
markdownNoThe generated guidance as a markdown document.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.19.15
    • addedInput schema / properties / platform / description
      Added value: +"`both` renders the native iOS and Android SDKs. `react_native` renders the React Native SDK for bare React Native apps and Expo development builds."
    • changedInput schema / properties / platform / enum
      Previous value: -[
      -  "ios",
      -  "android",
      -  "both"
      -]New value: +[
      +  "ios",
      +  "android",
      +  "both",
      +  "react_native"
      +]
    • changedOutput schema / description
      Previous value: -"Native iOS/Android SDK guidance, as a markdown document."New value: +"Native iOS/Android or React Native SDK guidance, as a markdown document."
  2. First observedv0.12.2

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's added value is the return format (Markdown) and the version-specific content scope, plus the explicit statement that no SDK is installed and no token is created. It stops short of describing auth requirements or whether the guide is cached/static, but for a documentation-fetch tool the disclosure is solid.

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?

Three sentences, front-loaded with what is returned and which versions, followed by tailoring controls, then exclusions and alternatives. No filler, and the most decision-relevant information (version, scope) comes first.

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-value explanation is unnecessary, and the description covers purpose, scope, exclusions, and alternatives for a documentation tool with zero required parameters. The residual gap is undocumented parameters, which matters less here because all parameters are optional and defaulted.

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 only 14%, so the description must carry parameter meaning and it only partially does: it names `platform`, `participantState`, and `includeInstallSnippets`, explaining that they 'tailor the guide' and 'control installation examples'. Three of seven parameters — `campaignId`, `mobilePublicKey`, `attributionProvider` — get no explanation in either place, and `serverVerifiedQualifyingAction` is unmentioned, leaving meaningful gaps for a 7-param tool.

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?

States a specific verb and resource ('Get Markdown implementation guidance') and pins exact SDK versions (native 0.10.6, React Native 0.3.4), plus the topical scope: attribution, `shareUrl`, `trackShare`, native GrowSurf Window. An agent can distinguish this from a generic integration guide or snippet tool without opening the schema.

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?

Explicitly names when-not-to-use ('Does not install an SDK or create a participant token') and routes to two named alternatives, `growsurf_client_snippets` for browser JavaScript and `growsurf_api_library_snippets` for backend token creation. The negative scope plus explicit sibling routing is exactly what selection guidance should look like.

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

Deploy Server

Other Tools