Skip to main content
Glama

The Bridge

by dev.thebridge
OverviewDiscussionsAdmin

Create Plan

create_plan

Create a new subscription plan with its first recurring price. Arguments: key (required — stable identifier used in code and billing, e.g. "pro"; flag rules point at the plan's features, not its key), name (required — the display name), amount + interval (the first price; amount 0 for a free or contact-sales tier: a plan with no price can never be assigned to a workspace), currency (ISO code) and trial (true or false), with trialDays when trial is true, and description. Price, interval, currency and trial are the developer's decisions: when one is missing (currency and trial are only needed when amount is above 0) the tool changes nothing and returns DECISION_NEEDED listing the questions to ask. Add more prices (e.g. yearly) with set_plan_price and usage quotas with set_plan_quota, or use apply_plan to create a plan with all its prices and quotas in one call; update_plan changes name, description and trial later. Returns the full plan. Count usage once, where the action happens: ask the developer whether the action calls their server. If it does, the backend decorator (@RequireQuota) counts it. If it does not, the browser reports it (bridge.usage.report / set) with on the button; that is a complete, first-class setup. Never count one metric in both places. Before writing app code that consumes this, call get_integration_guide with topic=billing and the framework the app uses.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appNoId of the Bridge app to act on for this call (see list_apps). Omit to use the current app.
keyYesPlan KEY: short, lower-case and permanent, e.g. "pro". Code and tokens use it; flag rules point at the plan's features instead.
nameYesDisplay name customers see, e.g. "Pro". Can change later.
trialNoWhether the plan has a free trial. Required when amount is above 0; ask the developer.
amountNoFirst recurring price amount. 0 for a free or contact-sales tier. Ask the developer.
currencyNoISO currency code, e.g. "USD". Required when amount is above 0; ask the developer.
intervalNoBilling recurrence interval.
trialDaysNoTrial length in days. Required when trial is true.
descriptionNoShort description shown with the plan.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only cover the generic safety profile (non-read-only, non-idempotent, non-destructive). The description adds behavior the agent could not infer: the DECISION_NEEDED no-op path when developer decisions are missing, the 'returns the full plan' outcome, and the quota-counting contract (backend decorator vs browser reporting, never both). That is substantive disclosure beyond structured fields.

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?

Core purpose and alternatives are front-loaded effectively, but the trailing paragraphs on quota counting and the integration guide are lengthy and only loosely tied to invoking create_plan. They add useful ecosystem context but dilute the tool's own call semantics.

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

Completeness5/5

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

For a 9-parameter creation tool with no output schema, the description supplies the missing return statement ('Returns the full plan'), the failure mode (DECISION_NEEDED), and the correct follow-up calls. Nothing an agent needs to invoke this correctly is absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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 real meaning on top: why key must be stable and that flag rules point at features not the key, that amount 0 is legitimate (free/contact-sales), and the conditional dependency currency/trial are only needed when amount is above 0, which the schema does not express as a rule.

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 plus scope ('Create a new subscription plan with its first recurring price'), immediately distinguishing it from siblings like set_plan_price and apply_plan. An agent can tell exactly what state this call leaves behind without opening any 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 routes to alternatives and conditions: add prices via set_plan_price, quotas via set_plan_quota, all-in-one via apply_plan, later edits via update_plan, and pre-work via get_integration_guide. It also states when the tool refuses (missing price/currency/trial decisions), which is real when-not guidance.

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

All The Bridge toolsInspect
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.

Resources