Skip to main content
Glama
pofky

asc-mcp

by pofky
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Start a free 7-day Pro trial

asc_start_trial

Unlock all 41 tools with a free 7-day Pro trial using just an email. If a Pro tool is refused, start the trial to retry it immediately in the same session.

Instructions

Start a free 7-day Pro trial, no credit card, unlocking all 41 tools including the full write/control plane. Call this when a Pro tool is refused and the user wants to proceed, and also when they ask for something only a Pro tool can do (editing metadata, screenshots, builds, TestFlight, IAP, submitting, releasing, preflight, briefings, keyword or review intelligence) before you hit the refusal. Either way, ask for their email address first and never invent one. The trial activates in THIS session immediately, so you can retry the tool that was blocked without any restart. Free.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toolNoThe tool whose gate prompted this, e.g. submit_for_review.
emailYesThe user's email address. Required: the trial key is sent there so they still have it later. Ask the user for it; never invent one. Tell them what the request stores: this address and a one-way hash of their Issuer ID, nothing else, and both are deletable at https://asc-mcp-license.remewdy.workers.dev/delete (policy: https://asc-mcp-license.remewdy.workers.dev/privacy).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.9.11
    • changedInput schema / properties / email / description
      Previous value: -"The user's email address. Required: the trial key is sent there so they still have it later. Ask the user for it; never invent one."New value: +"The user's email address. Required: the trial key is sent there so they still have it later. Ask the user for it; never invent one. Tell them what the request stores: this address and a one-way hash of their Issuer ID, nothing else, and both are deletable at https://asc-mcp-license.remewdy.workers.dev/delete (policy: https://asc-mcp-license.remewdy.workers.dev/privacy)."
  2. Added

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does a good job: it discloses that the trial is free, requires no credit card, activates immediately in the current session, and lets the agent retry the previously blocked tool. 'Never invent one' also communicates an important behavioral constraint.

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

Conciseness4/5

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

The description is front-loaded with the core action and includes useful trigger context. The list of Pro-only capabilities is slightly long but helps identify when to call; 'Free' is redundant after 'no credit card.'

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?

It covers the key workflow: when to call, what to ask for, what happens after activation, and how to proceed. It does not describe the exact return value or whether the trial can be repeated, but these are minor for this tool and no output schema is provided.

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 100%, so the baseline is 3. The description reinforces the email requirement but does not add much parameter-level meaning beyond what the schema already states for 'email' and '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?

The description opens with a specific action—'Start a free 7-day Pro trial'—and clearly distinguishes the tool from the surrounding app-store operation siblings. It also explains the unlock effect: 'all 41 tools including the full write/control plane.'

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 explicitly states when to call the tool: when a Pro tool is refused or when the user asks for something only a Pro tool can do. It does not explicitly state when not to use it or name an alternative, but the positive trigger conditions are specific and actionable.

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