Skip to main content
Glama

Set your business details

docx_business_set

Configure your business sender profile once to appear on proposals, contracts, letters, and invoices, including issuer and default VAT.

Instructions

The sender profile printed on every proposal, contract and letter. The SAME profile invoice's business_set writes: it goes to the shared profile, so it also sets your invoice issuer and default VAT.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
vatNoAlias for default_tax_rate
bankNoBank name / BIC
ibanNoIBAN or account number for payment
nameYesYour business or freelancer name, printed on the letterhead of every proposal, contract and letter
emailNoYour own email address, printed on every letterhead. Leave it out unless the user gave it: a document that shows an address nobody supplied is worse than one that shows [add: email]
phoneNoYour own phone number. Same rule as email: only if the user gave it
vat_idNoVAT / tax registration id
addressNoPostal address, newlines allowed
tax_rateNoAlias for default_tax_rate
timezoneNoIANA zone you work in, e.g. Europe/Warsaw. Shared with time-tracker and timezone as your home zone
vat_rateNoAlias for default_tax_rate
logo_pathNoPath to a PNG or JPG logo for the letterhead (Pro)
brand_colorNoLetterhead colour as a hex code, e.g. 1F3864 (Pro)
invoice_prefixNoReference prefix used by mcp-invoice; this profile has the same field shape as mcp-invoice, so one profile serves both
default_currencyNoISO code, e.g. EUR, USD. Default EUR
default_tax_rateNoDefault VAT percent, quoted on proposals
payment_terms_daysNoDefault days until payment is due. Default 14

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.20.0

TDQS

C2/5.0
Behavior2/5

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

The description vaguely mentions that changes go to a shared profile and affect invoice issuer and default VAT, but it does not clarify persistence, overwrite behavior, validation, or any other meaningful side effects. With no annotations, this is insufficient.

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?

The description is short, but the second sentence is confusing and poorly worded, making it less concise and harder to parse than a simple clear statement would be.

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 17 parameters, no output schema, and no examples, the description lacks crucial context such as return behavior, required-field implications, or how the shared profile relationship impacts callers.

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?

The schema provides descriptions for all 17 parameters, including aliases and defaults, so the description itself adds little parameter-level meaning. This meets the baseline but does not exceed it.

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?

The title 'Set your business details' is clear, and the description indicates it configures sender/profile information shown on documents. However, the body is garbled ('The SAME profile invoice's business_set writes:') and never plainly states that calling this tool updates the business profile.

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?

No guidance is provided on when to use this tool versus siblings like profile_set or invoice_business_set, nor are any prerequisites or expected call contexts mentioned.

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