Skip to main content
Glama

report_printer_overage

Report metered printer overage to Stripe by subtracting 20 included printers. Auto-detects active printer count from the fleet registry if not provided.

Instructions

Report metered printer usage to Stripe for Enterprise billing.

        Enterprise feature. The first 20 printers are included in the base
        Enterprise price ($499/mo). This tool **automatically subtracts** the
        20 included printers and reports only the overage count to Stripe's
        ``active_printers`` meter at $15/printer/month.

        If *active_printer_count* is omitted, the fleet registry is queried
        automatically — no manual counting needed.

        Args:
            subscription_item_id: The Stripe SubscriptionItem ID (``si_...``) for
                the metered printer overage line item on the customer's subscription.
            active_printer_count: Total number of active printers.  Leave empty
                to auto-detect from the fleet registry.

        Example:
            With 25 registered printers, this reports **5** to Stripe
            (25 − 20 included = 5 overage × $15 = $75/mo).
        

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
active_printer_countNo
subscription_item_idYes
Behavior5/5

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

The description fully discloses behavioral traits: automatic subtraction of 20 printers, reporting to Stripe meter, and auto-detection of printer count. Since no annotations are provided, the description carries the full burden and meets it comprehensively.

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 well-structured with a clear purpose statement, business logic, parameter details, and an illustrative example. Every sentence adds value, and key information is front-loaded.

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?

The description covers all necessary aspects: purpose, business context, parameter behavior, and an example with concrete numbers. For a tool with no output schema, this is fully complete.

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

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description includes an 'Args:' section that explains both parameters (subscription_item_id and active_printer_count) with details on required format and auto-detection behavior. This adds significant meaning beyond the input schema's basic structure.

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 clearly states the tool's purpose: 'Report metered printer usage to Stripe for Enterprise billing.' It explains the business logic (subtracting 20 included printers) and distinguishes it from sibling tools as a billing-specific function.

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?

The description explains when to use the tool (for Enterprise billing overage) and provides guidance on the optional parameter (auto-detect from fleet registry). However, it does not explicitly mention when not to use or list alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/codeofaxel/kiln'

If you have feedback or need assistance with the MCP directory API, please join our Discord server