Start checkout for a Scriptivox web subscription and return a Stripe Checkout URL. Does NOT charge anything: the person must open the link and enter their card. A web plan covers transcription done by a person in the browser and grants no API credit. Requires an OAuth 2.1 user access token.
| Name | Required | Description | Default |
|---|---|---|---|
| plan | Yes | Which plan to buy. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds important behavioral details beyond the annotations: it 'Does NOT charge anything' and clarifies the user must complete payment by opening the link. It also states the auth requirement. This meaningfully supplements the basic readOnlyHint/idempotentHint flags without contradicting them.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three tightly written sentences deliver the action, the key safety clarification, the product scope, and the auth requirement. Every sentence contributes necessary information and the most important caveat is front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple one-parameter tool, the description covers what the tool does, what it returns, the auth requirement, and the crucial 'no charge' behavior. It does not mention possible errors or edge cases, but given the low complexity and presence of the enum schema, this is a minor gap.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema already documents the single required parameter with an enum and a description. The description adds context about what a web plan is and that it excludes API credit, but it does not explain the difference between 'monthly', 'yearly', and 'team' beyond the schema. This meets the baseline for high schema coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description opens with a specific verb and resource: 'Start checkout for a Scriptivox web subscription and return a Stripe Checkout URL.' It clearly identifies what the tool does, what it returns, and separates it from related billing and account tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The context for use is clear: it is for purchasing a web subscription via Stripe Checkout, and it notes the OAuth 2.1 user access token requirement. It does not explicitly name alternatives or exclusion conditions, but the product scoping ('grants no API credit') helps an agent distinguish when this is the wrong tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
The set contains several near-neighbor groups: deprecated aliases duplicate live tools, and docs/billing/financial tools have fuzzy boundaries. Individual descriptions are detailed and resolve most collisions, but matching the right tool among 39 still requires care.
Most tools follow a sensible verb_object style, but the transcribe_* group is inconsistent: transcribe_url/transcribe_upload are verb_object, while transcribe_status/transcribe_cancel/transcribe_delete are really status/cancel/delete operations renamed with a transcribe prefix. The deprecated transcription_status/transcription_url aliases add another naming convention, so the pattern is not reliable across the set.
39 tools is well over the 25+ threshold and creates an overwhelmingly broad surface spanning account management, billing, docs, API jobs, library organization, meeting bots, and automations. Two deprecated duplicates inflate the count further. This would be more coherent split into separate servers or at least pruned of deprecated aliases.
Core API transcription lifecycle is covered, and the library/meeting-bot flows have search, tagging, moving, and audio retrieval. However, there is no user-library deletion/rename, no OAuth-side full-transcript access, local upload is non-functional over the hosted endpoint, and webhook management is documented but not exposed as tools. These gaps force agents to work around missing operations.
