Skip to main content
Glama
jstibal

Openterms-mcp

list_receipts

Retrieve recent workspace receipts to track cryptographic consent proofs, filter by action type, and monitor spending caps with verifiable records.

Instructions

List recent receipts for this workspace.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax receipts to return (default 10, max 50)
action_typeNoFilter by action type

Implementation Reference

  • The handler implementation for the list_receipts tool, which makes a GET request to the /v1/receipts API endpoint and formats the results.
    elif name == "list_receipts":
        params = {}
        if arguments.get("limit"):
            params["limit"] = min(arguments["limit"], 50)
        if arguments.get("action_type"):
            params["action_type"] = arguments["action_type"]
        resp = client.get("/v1/receipts", params=params, headers=_headers())
        if resp.status_code == 200:
            data = resp.json()
            receipts = data.get("receipts", data) if isinstance(data, dict) else data
            if not receipts:
                return "No receipts found."
            lines = [f"Found {len(receipts)} receipt(s):"]
            for r in receipts[:10]:
                lines.append(
                    f"  [{r.get('action_type')}] {r.get('receipt_id', '?')[:12]}... "
                    f"— {r.get('terms_url', '?')} ({r.get('created_at', '?')})"
                )
            if len(receipts) > 10:
                lines.append(f"  ... and {len(receipts) - 10} more")
            return "\n".join(lines)
        return _format_error(resp)
  • The schema definition for the list_receipts tool, defining the accepted input parameters.
        "name": "list_receipts",
        "description": "List recent receipts for this workspace.",
        "inputSchema": {
            "type": "object",
            "properties": {
                "limit": {"type": "integer", "description": "Max receipts to return (default 10, max 50)"},
                "action_type": {"type": "string", "description": "Filter by action type"},
            },
        },
    },
Behavior2/5

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

No annotations provided, so description carries full burden. 'List' implies read-only but doesn't confirm safety or idempotency. Critical gaps: undefined time window for 'recent', no mention of default sorting (chronological?), pagination behavior beyond the limit parameter, or whether deleted/failed receipts are included.

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?

Single sentence, six words, front-loaded with action verb. No redundant or filler text. Appropriate length for the tool's apparent simplicity, though underspecified for behavioral completeness.

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

Completeness2/5

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

For a list operation with no output schema and no annotations, the description should clarify return structure, pagination behavior, or the definition of 'recent'. With only 2 optional parameters and simple schema, the lack of behavioral context (time windows, sorting) leaves significant gaps in agent understanding.

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 has 100% description coverage, establishing baseline 3. Description adds 'this workspace' context (indicating implicit workspace scoping from connection context) but doesn't clarify what 'action_type' values are valid or that 'recent' implies a time-based query despite no explicit date parameters in schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses specific verb 'List' with clear resource 'receipts' and scope ('recent', 'this workspace'). However, it lacks explicit differentiation from sibling tools like 'verify_receipt' or 'issue_receipt', though the operation type (list vs verify/issue) is implied by the verb choice.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit when-to-use guidance or alternatives mentioned. The phrase 'recent receipts' provides minimal temporal context, but there's no guidance on when to use this versus 'verify_receipt' for specific receipt lookup, or how 'recent' is defined (time window vs count).

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