Paydirt MCP

Official

Overview Schema Source Related Servers Discussions Admin

paydirt_begin_setup

Install voice cancellation feedback and feature request forms in an iOS app by starting setup, reusing an existing app or creating a new one, and connecting Slack during browser authorization.

Instructions

Use this when installing voice cancellation feedback or Suggest a Feature for an iOS app with RevenueCat or StoreKit, and connect Slack during browser authorization. For website-started setup, pass its app_id to reuse the prepared app and delivery settings. Inspect the host first. Without form_plan_confirmed, returns the concise cancellation/Suggest a Feature confirmation and does not start authorization. After confirmation, pass the selected use_cases and placement to receive authorization_url and finish_arguments immediately.

Input Schema

TableJSON Schema

Name	Required	Description
`app_id`	No	Existing Paydirt app ID, including the ID in a website setup handoff. Reconnect this exact app and reuse its saved Slack/delivery settings instead of creating another app.
`app_name`	No	Preferred app name to reuse or create during setup
`bundle_id`	No	Preferred iOS bundle ID to match during setup
`use_cases`	No	Confirmed feedback experiences to install. The recommended plan is Suggest a Feature plus trial and paid cancellation when subscriptions exist.
`app_description`	No	Optional app description to save when creating or repairing setup
`uses_revenuecat`	No	Deprecated compatibility input. Prefer subscription_provider.
`feature_placement`	No	Developer-confirmed placement for Suggest a Feature, such as settings or after_successful_export. Defaults to settings.
`form_plan_confirmed`	No	Set true when the developer explicitly requested these voice forms or confirmed the proposed plan. An explicit installation request already confirms its scope; do not ask the same question again. Ask only when the requested forms or placement are ambiguous.
`subscription_provider`	No	Subscription source of truth discovered in the host app. Use auto only when it could not be resolved before setup.
`subscription_product_ids`	No	Native StoreKit auto-renewable product IDs. Required for a complete storekit integration.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`status`	Yes
`message`	No
`success`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv2.4.0Sep 8, 2026

addedInput schema / properties / app_id

Added value: +{
+  "description": "Existing Paydirt app ID, including the ID in a website setup handoff. Reconnect this exact app and reuse its saved Slack/delivery settings instead of creating another app.",
+  "type": "string"
+}

addedInput schema / properties / feature_placement

Added value: +{
+  "description": "Developer-confirmed placement for Suggest a Feature, such as settings or after_successful_export. Defaults to settings.",
+  "type": "string"
+}

addedInput schema / properties / form_plan_confirmed

Added value: +{
+  "description": "Set true when the developer explicitly requested these voice forms or confirmed the proposed plan. An explicit installation request already confirms its scope; do not ask the same question again. Ask only when the requested forms or placement are ambiguous.",
+  "type": "boolean"
+}

changedInput schema / properties / use_cases / description

Previous value: -"Feedback experiences to install. Defaults to regular feedback, trial cancellation, and subscription cancellation."New value: +"Confirmed feedback experiences to install. The recommended plan is Suggest a Feature plus trial and paid cancellation when subscriptions exist."

changedInput schema / properties / use_cases / items / enum

Previous value: -[
-  "regular_feedback",
-  "trial_cancellation",
-  "subscription_cancellation"
-]New value: +[
+  "regular_feedback",
+  "feature_request",
+  "trial_cancellation",
+  "subscription_cancellation"
+]

First observedv2.1.6Aug 1, 2026

TDQS

A3.5/5.0

Behavior3/5

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

The description clearly says that without form_plan_confirmed it will not start authorization, and that after confirmation it returns authorization_url and finish_arguments. It does not disclose side effects such as creating or updating apps, whether the operation is idempotent, or what happens if required steps are skipped.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with 'Use this when' and includes only relevant workflow information. However, it is a single dense run-on paragraph with awkward phrasing like 'voice cancellation feedback' and 'concise cancellation/Suggest a Feature confirmation', making it less clear than it should be.

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

Completeness3/5

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

Given the multi-step setup flow, the description covers the main state transition (confirmation before authorization, then receiving authorization_url) and mentions app_id reuse. It lacks specifics about how to inspect the host, what the output schema contains, or failure/error conditions, but it does provide enough for basic use.

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 100%, so the baseline is 3. The description adds flow context for app_id, use_cases, form_plan_confirmed, and feature_placement, but most parameter meaning already lives in the schema and several parameters like app_name, subscription_product_ids, and uses_revenuecat are not enriched.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the specific action—beginning setup for feedback forms and Slack connection—and gives enough detail to distinguish it from siblings like paydirt_setup and paydirt_finish_setup. However, the phrase 'voice cancellation feedback' is confusing and likely a typo, which prevents a perfect score.

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?

It states when to use the tool (installing feedback forms, connecting Slack, browser authorization), how to handle website-started setups via app_id, and the confirmation gate before authorization. The instruction 'Inspect the host first' is vague and no explicit alternatives are mentioned, so it falls short of 5.

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