Skip to main content
Glama
ptrinh

Final Notice

preview_demand_letter

Review demand letter text content as structured JSON before final PDF generation. Refine wording, check legal references, and verify all fields.

Instructions

Render the demand letter's text content (title, subject, body paragraphs, amount line, legal reference, closing) as structured JSON, without producing a PDF. Use to review or refine wording before generating.

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?

With no annotations, the description carries the full burden. It states the tool renders text as JSON and does not produce a PDF, which is helpful. However, it does not disclose other behavioral traits like idempotency, rate limits, or side effects. The description is adequate but could be more transparent.

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, front-loading the core action and output format, then stating the use case. Every sentence adds value with no redundancy or fluff.

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

Completeness3/5

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

Despite the tool's complexity (23 parameters, nested objects, no output schema), the description is concise. However, it lacks detail on the return structure beyond listing a few components. Since there is no output schema, the description should more fully explain the JSON output format to be complete.

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 coverage is 100%, so the baseline is 3. The description adds some context about output structure (title, subject, body, etc.) but does not elaborate on individual parameters beyond what the schema already provides. Thus, no additional value for parameter semantics.

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 the tool renders the demand letter's text content as structured JSON without producing a PDF, specifying the output components. It distinguishes itself from the sibling generate_demand_letter by noting it's for previewing before generating.

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?

The description explicitly says 'Use to review or refine wording before generating,' providing clear context and implying the tool is for preview before final PDF generation. It distinguishes from generate_demand_letter which produces the PDF, but does not explicitly state when not to use.

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