Skip to main content
Glama

business_donation_receipt

Read-onlyIdempotent

Donation receipt maker

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "organizationName": "<organizationName>",
      "ein": "<ein>",
      "donorName": "<donorName>",
      "date": "<date>"
    },
    "name": "business_donation_receipt"
  }
}

Input Schema

NameRequiredDescriptionDefault
einYesThe charity's Employer Identification Number, 9 digits (12-3456789 or 123456789). Printed on the receipt; a malformed number is a 422.
dateYesDate the gift was received, YYYY-MM-DD, a real date.
amountNoCash: the total the donor paid, in US dollars. Needed for cash. For two $150 tickets send 300.
donorNameYesWho gave.
eventNameNoEvent or campaign, for example 'Spring Gala'.
signerNameNoWho signs for the charity.
includeDocxNotrue also returns the receipt as a Word file in result.docx (filename, contentType, base64).
signerTitleNoSigner's title.
donorAddressNoDonor address (optional).
exemptionTypeNoSection of the Internal Revenue Code that exempts the charity. Default 501(c)(3).
receiptNumberNoYour receipt number.
contributionTypeNocash (default) states the amount; noncash describes the property and states no value, as the IRS requires.
goodsAndServicesNoWhat the donor received in return (dinner, ticket, merchandise). Leave out when nothing was given. The deductible amount is the amount paid less their value.
organizationNameYesThe charity's legal name.
organizationAddressNoCharity address, printed under the name.
propertyDescriptionNoNon-cash: what was given. Needed for noncash. Do not put a value on it.
intangibleReligiousBenefitsOnlyNotrue when the only benefit was intangible religious benefits (for a religious organization); prints that statement instead of a goods and services list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / goodsAndServices / items / additionalProperties
      Removed value: -false
    • addedInput schema / properties / goodsAndServices / items / properties / description / description
      Added value: +"What the donor received in return, for example Dinner for two."
  2. Added

TDQS

D1.9/5.0
Behavior2/5

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

Annotations declare readOnlyHint, idempotentHint, and non-destructive, so safety is covered, but the description adds nothing further. It does not mention that a document is produced, that includeDocx can return a Word file, or that IRS-specific rules change output based on contributionType.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three words are technically concise but reflect under-specification rather than economy. There is no front-loaded statement of what the tool produces or requires.

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

Completeness1/5

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

A 17-parameter IRS-compliant receipt generator with no output schema deserves far more than a four-word label. Nothing in the description explains document generation, required legal fields, or the noncash/cash branching that the schema encodes.

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 description coverage is 100% and the parameter descriptions are detailed (EIN formatting, contributionType behavior, goodsAndServices deductible-amount logic), so the schema carries all parameter meaning. The description adds none, making the baseline 3 appropriate.

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

Purpose2/5

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

"Donation receipt maker" essentially restates the tool name and title, only barely distinguishing it from the sibling business_receipt by the word "donation". It never states a verb like generate/create or what the output actually is (a formatted receipt, optionally a .docx).

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

Usage Guidelines1/5

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

The description gives no when-to-use guidance, no prerequisites, and no indication of how this differs from business_receipt or the other business document generators. An agent must infer everything from the tool name alone.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources