Skip to main content
Glama
jstibal

Openterms-mcp

get_pricing

Retrieve current per-receipt pricing for the OpenTerms protocol. Public access requires no API key.

Instructions

Get current per-receipt pricing. Public — no API key needed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Tool registration for 'get_pricing' in the TOOLS list — defines the name, description, and inputSchema (no inputs required).
        "name": "get_pricing",
        "description": "Get current per-receipt pricing. Public — no API key needed.",
        "inputSchema": {"type": "object", "properties": {}},
    },
  • Handler function for 'get_pricing' — makes a GET request to /v1/pricing (no auth), returns pricing version, per-receipt cost in USDC minor units, and currency.
    elif name == "get_pricing":
        resp = client.get("/v1/pricing", headers=_headers(auth=False))
        if resp.status_code == 200:
            p = resp.json()
            return (
                f"Pricing version: {p.get('version', '?')}\n"
                f"  Per receipt: {p.get('per_receipt', '?')} USDC minor units\n"
                f"  Currency: {p.get('currency', 'USDC')}"
            )
        return _format_error(resp)
  • CLI wrapper — calls handle_tool('get_pricing', {}) when CLI command 'pricing' is used.
    if cmd == "pricing":
        print(handle_tool("get_pricing", {}))
  • Server-side API endpoint for /v1/pricing — returns pricing info (version, price_per_receipt, currency, free_mode). This is what the MCP handler calls via HTTP GET.
    @app.route('/v1/pricing', methods=['GET'])
    def get_pricing():
        if FREE_MODE:
            return jsonify({
                "version": PRICING_VERSION,
                "price_per_receipt": 0,
                "currency": "USDC",
                "decimals": 6,
                "free_mode": True,
                "message": "Receipt issuance is free during beta.",
            })
        return jsonify({
            "version": PRICING_VERSION,
            "price_per_receipt": PRICE_PER_RECEIPT,
            "currency": "USDC",
            "decimals": 6,
            "free_mode": False,
        })
Behavior3/5

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

Describes public access (no auth needed), but no annotations are provided. Does not disclose return format or any limits; minimal but acceptable for a zero-parameter tool.

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?

Two sentences, no extraneous information. Front-loaded with action and key detail.

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?

Adequate for a simple public tool with no parameters. Could mention return structure, but not essential given the tool's simplicity.

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?

No parameters; schema coverage is 100%. Description adds meaning by specifying 'per-receipt pricing', clarifying the scope beyond the empty schema.

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?

Clearly states verb 'Get' and resource 'current per-receipt pricing'. Adds context about public access, distinguishing it from other tools like check_balance or get_policy.

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?

Specifies that the tool is public with no API key required, providing immediate guidance on authentication. However, lacks explicit when-to-use vs alternatives, though no alternatives exist.

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/jstibal/openterms-mcp'

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