Skip to main content
Glama
SubscriptionTech

ProAbono MCP Installation

Official
by SubscriptionTech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List the offers of the account

list_offers

Fetch the full offer catalogue for the configured Segment, including features and pricing, by reading all pages. Use it to display pricing, select target offers, or verify at least one offer has a feature.

Instructions

Lists the ProAbono offers the configured Segment exposes, with the Features each one carries and its pricing. Read-only. This is the catalogue: what the merchant sells, to anyone. Use it to show a pricing page, to pick the offer a subscription or a pricing table targets, or to check the prerequisite that at least one offer exists and carries at least one Feature. For what one named customer may take, or what a running subscription can move to, use list_offers_for_customer instead. Reads every page, not just the first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
visible_onlyNoOnly offers marked visible.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.1
    • removedInput schema / properties / customer_ref
      Removed value: -{
-  "description": "Restrict to the offers available to this customer reference.",
-  "type": "string"
-}
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It clearly states 'Read-only' and reveals pagination behavior with 'Reads every page, not just the first,' which is valuable context beyond the schema. It does not mention response size or potential cost of reading every page, but for a read-only catalogue listing this is a strong disclosure.

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?

The description is front-loaded with the core function, then efficiently adds use cases, the sibling alternative, and an important pagination trait. Every sentence contributes information needed for correct selection and invocation, with no filler.

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?

With no output schema, the description compensates by summarizing the return contents: the offers, their Features, and pricing. It also covers scope, read-only behavior, pagination, and alternatives. It does not describe the exact response shape, but for a low-complexity list operation the provided context is nearly complete.

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?

The input schema already documents the single optional visible_only parameter with 100% coverage. The description does not add parameter-level semantics, but the high schema coverage means the baseline of 3 is appropriate.

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 states a specific action and resource: lists the ProAbono offers exposed by the configured Segment, including features and pricing. It explicitly distinguishes itself from the sibling list_offers_for_customer by name, so an agent can tell them apart at a glance.

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?

It gives concrete use cases: showing a pricing page, selecting an offer for a subscription or pricing table, and validating the prerequisite that at least one offer with a Feature exists. It also gives an explicit when-not-to-use instruction, pointing to list_offers_for_customer for customer-specific or subscription-specific offer queries.

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