Skip to main content
Glama
SubscriptionTech

ProAbono MCP Installation

Official
by SubscriptionTech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Install the ProAbono Customer Portal in a page

install_customer_portal

Generate integration code that embeds the ProAbono Customer Portal on a merchant's own site for authenticated customers, including security hash, route, and template snippet.

Instructions

Generates the code that embeds the ProAbono Customer Portal inside a page of the merchant's own site -- current plan, invoices, payment method, billing address, usage -- for the signed-in customer. This is step 1 of the In-Site installation. Returns the server-side security hash computation, the route that renders the page, and the snippet to place in the template. Requires an authenticated customer area: the hosted pages always render for an identified customer.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stackYesThe host project's stack. Detect it from the open project (package.json, composer.json, requirements.txt, Gemfile, .csproj) and confirm with the developer. Use "generic" when none fits.
target_pageYesPath of the page that will host the portal, e.g. "/account/billing".
pass_languageNoPass the application's UI language to ProAbono. Only when the application is the authority for it: it overwrites what the customer set in the portal.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and does well: it clarifies the tool generates code rather than performing the installation, lists the returned artifacts, and discloses the authentication requirement. It could add more about side effects or failure conditions, but the core behavior is transparent.

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?

Four sentences, each carrying distinct value: purpose, installation step, return artifacts, and authentication constraint. There is no filler or repetition, and the most important orientation is front-loaded.

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?

For a tool with no output schema, the description gives a solid high-level picture of what is returned and the prerequisite condition. It could be more complete by hinting at what follows step 1 or describing the returned snippet format, but nothing essential is missing for calling the tool.

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 schema already documents all three parameters. The description adds installation context but does not enrich parameter meaning beyond the schema, matching the baseline for high coverage.

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 ('Generates the code that embeds the ProAbono Customer Portal inside a page'), names the customer-facing content covered, and distinguishes this from sibling code-generation tools by calling out 'This is step 1 of the In-Site installation'. An agent can tell what this tool produces and how it relates to the installation flow.

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?

Provides clear context for when to use it: it is the first step of the In-Site installation and requires an authenticated customer area. It does not explicitly name alternatives or say when not to use it, so it stops short of a 5, but the context is strong enough to guide selection.

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