Skip to main content
Glama

AskAIs AI Receipt Generator

by io.github.MiniCodeTeam

Generate a professional receipt PDF

generate_receipt

Generate a downloadable receipt PDF for a legitimate transaction. Costs $0.10 only on successful generation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoReceipt date, preferably YYYY-MM-DD.
itemsNo
notesNo
api_keyNoOptional after create_free_account succeeds in this MCP session.
currencyNoCurrency symbol or code, for example USD, HKD, or $.
languageNo
text_colorNo
total_amountNo
customer_nameYes
primary_colorNo
contact_personNo
customer_emailNo
customer_notesNo
customer_phoneNo
invoice_numberNo
payment_methodNo
customer_addressNo
customer_registration_numberNo
confirm_legitimate_transactionYesMust be true. Confirms this receipt represents a legitimate transaction and will not be used to deceive.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description must cover behavioral traits. It mentions cost ($0.10 on success) but omits idempotency, state changes, authentication needs, or failure behavior. Insufficient for a tool with financial implications.

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?

Extremely concise with two sentences, front-loaded with purpose and cost. No redundant information.

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?

Given 19 parameters, no output schema, and required confirm_legitimate_transaction, the description lacks critical context such as output format, how to retrieve the PDF, or how items array works. Incomplete for reliable invocation.

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

Parameters1/5

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

Schema coverage is low (21%), so description should compensate, but it adds no parameter semantics. The description does not explain any of the 19 parameters beyond what the schema provides.

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 it generates a downloadable receipt PDF for a legitimate transaction, uses a specific verb and resource, and the cost is mentioned, distinguishing it from sibling tools like create_free_account.

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

Usage Guidelines3/5

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

No explicit guidance on when to use this tool vs alternatives. The api_key parameter description notes optionality after account creation, but overall lacks contextual usage direction.

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

All AskAIs AI Receipt Generator toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation5/5

Each tool has a clear, distinct purpose: account creation, receipt generation, balance checking, and rules reading. There is no overlap or ambiguity.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern in snake_case: create_free_account, generate_receipt, get_balance, get_usage_rules.

Tool Count5/5

With 4 tools, the set is appropriately scoped for a receipt generation service, covering account management, generation, balance, and rules.

Completeness4/5

The core workflow is covered (account, generation, balance, rules), but missing features like viewing past receipts or deleting accounts are minor gaps.

Resources