Skip to main content
Glama
ptrinh

Final Notice

generate_demand_letter

Generate a legally formatted demand letter PDF with matching envelope, localized for the debtor's jurisdiction. Free and requires no registration.

Instructions

Generate the finished demand-letter PDF (formal letter + matching envelope), localized and legally formatted for the jurisdiction. Returns the PDF as a base64 resource. Free, no registration.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bankNoPayment/bank details keyed by field (e.g. {bankName, iban, accountNumber}). Optional.
toneNoEscalation level. Default: final.
amountYesAmount owed, as a number (no separators). Required, > 0.
attestedNoConfirms authorization to send under the sender name. Required when senderType is business/firm.
currencyNoISO 4217 currency (optional; defaults to the jurisdiction's).
languageNoLetter language code (e.g. en, es, fr, de, pt, ar, zh, ja). Must be offered for the jurisdiction; defaults to en.
senderRefNoCreditor's own reference number (optional).
debtorNameYesDebtor name. Required.
debtorTypeNoWhether the debtor is a private individual (consumer) or a business. 'individual' activates jurisdiction consumer rules (e.g. GB Pre-Action Protocol 30-day floor, NL WIK wording). Default: business.
enclosuresNoEnclosed documents, printed as 'Encl.: …' under the signature (e.g. 'Copy of invoice INV-123'). Optional.
senderNameYesCreditor name (person or business). Required.
senderTypeNoCreditor type. Business/firm requires attested=true.
signerNameNoName of the person signing (optional; defaults to senderName).
descriptionNoWhat the debt is for (optional).
senderTitleNoSigner's job title (optional).
deadlineDaysNoDays from issue to pay (optional; default 14).
jurisdictionNoISO 3166-1 alpha-2 country code of the debtor (e.g. US, GB, DE, BR, AE). Use list_jurisdictions for the full set; XX = generic/international.
originalDateNoISO date the debt was incurred/invoiced (optional).
debtorAddressYesDebtor postal address, multi-line. Required.
invoiceNumberNoInvoice/account number (optional).
senderAddressYesCreditor postal address, multi-line (\n separated). Required.
senderContactNoCreditor email/phone (optional).
deliveryMethodNoHow the letter is sent; printed as a notation above the recipient (e.g. 'By registered post and email'). Optional.
Behavior3/5

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

Without annotations, the description carries full responsibility for behavioral transparency. It mentions that the PDF is returned as a base64 resource and that it is 'localized and legally formatted', but it does not disclose whether the tool modifies any state, requires authentication, has rate limits, or error handling. The nature of document generation is implicitly safe, but the description is minimal.

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 two sentences, clearly front-loading the primary output. Every sentence provides useful information: the first states what is generated, the second states the return format and pricing/registration status. No unnecessary words.

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 the tool's complexity (23 parameters, nested objects, no output schema), the description is too brief. It fails to explain the return structure beyond base64, does not mention the bank object nesting, and does not link to sibling tools for previewing or listing jurisdictions. An agent would need additional context to use this tool correctly.

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?

All 23 parameters have descriptions in the schema (100% coverage), so the description adds only marginal value (e.g., mentioning localization). The description itself does not elaborate on parameter semantics beyond what the schema provides, so a baseline score of 3 is appropriate.

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 states 'Generate the finished demand-letter PDF (formal letter + matching envelope)', which is a specific verb ('Generate') and resource ('demand-letter PDF'). It clearly distinguishes from sibling tools like preview_demand_letter by emphasizing 'finished' and 'matching envelope'.

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?

The description does not explicitly guide when to use this tool over siblings (preview_demand_letter, list_jurisdictions). It only mentions 'Free, no registration' which is not usage guidance. There is no mention of prerequisites such as first listing jurisdictions or previewing.

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/ptrinh/finalnotice-mcp'

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