Skip to main content
Glama

business_offer_letter_draft

Read-onlyIdempotent

Employment offer letter draft

Input Schema

NameRequiredDescriptionDefault
stateNoGoverning-law state or country. The governing-law section is left out when this is not sent.
titleYesThe job title.
salaryNoPay as a number or text: 92000, "$92,000", "92,000 per year", "6,000/month", "45 per hour". Must be above 0 (422 otherwise). Required, except for an unpaid internship. Words after the number set the period unless salaryPeriod is sent.
companyYesThe employer's name.
benefitsNoPermanent roles: the benefits paragraph. A standard sentence is used when left out.
candidateYesFull name of the person receiving the offer.
equipmentNoWhose equipment is used. Default company.
startDateYesFirst day of work as a real calendar date, YYYY-MM-DD (422 otherwise). A date in the past is allowed and returned as a warning.
mentorNameNoInternships: the mentor named in the reporting section.
noticeDaysNoWith termination notice: days of written notice. Default 30.
signerNameNo
includeDocxNotrue also returns the letter as a Word file in result.docx (filename, contentType, base64).
managerNameNo
signerTitleNo
terminationNoDefault at-will.
durationUnitNoDefault months.
managerTitleNo
positionTypeNoDefault permanent.
salaryPeriodNoWhat the pay is per. Default year, or the period named in the salary text.
contingenciesNoWhich conditions the offer depends on. Defaults: criminalCheck and workEligibility true, the others false.
companyTaglineNo
durationNumberNoInternships: how long it lasts, in durationUnit. Default 3.
employmentTypeNoFull-time (default), Part-time, Contract.
learningPointsNoInternships: what the intern will gain, one item each. A standard list is used when left out.
paidInternshipNoInternships: true when a stipend is paid (then salary is the stipend). Default false: an unpaid-internship clause is written.
responseDeadlineNoLast day to accept, YYYY-MM-DD, on or before startDate (422 otherwise).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / candidate / description
      Previous value: -"The candidate's name."New value: +"Full name of the person receiving the offer."
  2. Changed34 schema fields changed
    • addedInput schema / properties / benefits
      Added value: +{
      +  "description": "Permanent roles: the benefits paragraph. A standard sentence is used when left out.",
      +  "maxLength": 2000,
      +  "type": "string"
      +}
    • addedInput schema / properties / candidate / description
      Added value: +"The candidate's name."
    • addedInput schema / properties / candidate / maxLength
      Added value: +200
    • addedInput schema / properties / company / description
      Added value: +"The employer's name."
    • addedInput schema / properties / company / maxLength
      Added value: +200
    • addedInput schema / properties / companyTagline
      Added value: +{
      +  "maxLength": 200,
      +  "type": "string"
      +}
    • addedInput schema / properties / contingencies
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "Which conditions the offer depends on. Defaults: criminalCheck and workEligibility true, the others false.",
      +  "properties": {
      +    "backgroundCheck": {
      +      "type": "boolean"
      +    },
      +    "criminalCheck": {
      +      "type": "boolean"
      +    },
      +    "referenceCheck": {
      +      "type": "boolean"
      +    },
      +    "workEligibility": {
      +      "type": "boolean"
      +    }
      +  },
      +  "type": "object"
      +}
    • addedInput schema / properties / durationNumber
      Added value: +{
      +  "description": "Internships: how long it lasts, in durationUnit. Default 3.",
      +  "maximum": 260,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / durationUnit
      Added value: +{
      +  "description": "Default months.",
      +  "enum": [
      +    "weeks",
      +    "months"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / employmentType
      Added value: +{
      +  "description": "Full-time (default), Part-time, Contract.",
      +  "maxLength": 40,
      +  "type": "string"
      +}
    • addedInput schema / properties / equipment
      Added value: +{
      +  "description": "Whose equipment is used. Default company.",
      +  "enum": [
      +    "company",
      +    "own"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / includeDocx
      Added value: +{
      +  "description": "true also returns the letter as a Word file in result.docx (filename, contentType, base64).",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / learningPoints
      Added value: +{
      +  "description": "Internships: what the intern will gain, one item each. A standard list is used when left out.",
      +  "items": {
      +    "maxLength": 300,
      +    "type": "string"
      +  },
      +  "maxItems": 20,
      +  "type": "array"
      +}
    • addedInput schema / properties / managerName
      Added value: +{
      +  "maxLength": 200,
      +  "type": "string"
      +}
    • addedInput schema / properties / managerTitle
      Added value: +{
      +  "maxLength": 200,
      +  "type": "string"
      +}
    • addedInput schema / properties / mentorName
      Added value: +{
      +  "description": "Internships: the mentor named in the reporting section.",
      +  "maxLength": 200,
      +  "type": "string"
      +}
    • addedInput schema / properties / noticeDays
      Added value: +{
      +  "description": "With termination notice: days of written notice. Default 30.",
      +  "maximum": 365,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / paidInternship
      Added value: +{
      +  "description": "Internships: true when a stipend is paid (then salary is the stipend). Default false: an unpaid-internship clause is written.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / positionType
      Added value: +{
      +  "description": "Default permanent.",
      +  "enum": [
      +    "permanent",
      +    "internship"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / responseDeadline
      Added value: +{
      +  "description": "Last day to accept, YYYY-MM-DD, on or before startDate (422 otherwise).",
      +  "maxLength": 20,
      +  "type": "string"
      +}
    • addedInput schema / properties / salary / anyOf
      Added value: +[
      +  {
      +    "maxLength": 60,
      +    "type": "string"
      +  },
      +  {
      +    "type": "number"
      +  }
      +]
    • addedInput schema / properties / salary / description
      Added value: +"Pay as a number or text: 92000, \"$92,000\", \"92,000 per year\", \"6,000/month\", \"45 per hour\". Must be above 0 (422 otherwise). Required, except for an unpaid internship. Words after the number set the period unless salaryPeriod is sent."
    • removedInput schema / properties / salary / minLength
      Removed value: -1
    • removedInput schema / properties / salary / type
      Removed value: -"string"
    • addedInput schema / properties / salaryPeriod
      Added value: +{
      +  "description": "What the pay is per. Default year, or the period named in the salary text.",
      +  "enum": [
      +    "year",
      +    "month",
      +    "hour"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / signerName
      Added value: +{
      +  "maxLength": 200,
      +  "type": "string"
      +}
    • addedInput schema / properties / signerTitle
      Added value: +{
      +  "maxLength": 200,
      +  "type": "string"
      +}
    • addedInput schema / properties / startDate / description
      Added value: +"First day of work as a real calendar date, YYYY-MM-DD (422 otherwise). A date in the past is allowed and returned as a warning."
    • addedInput schema / properties / startDate / maxLength
      Added value: +20
    • addedInput schema / properties / state
      Added value: +{
      +  "description": "Governing-law state or country. The governing-law section is left out when this is not sent.",
      +  "maxLength": 100,
      +  "type": "string"
      +}
    • addedInput schema / properties / termination
      Added value: +{
      +  "description": "Default at-will.",
      +  "enum": [
      +    "at-will",
      +    "notice"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / title / description
      Added value: +"The job title."
    • addedInput schema / properties / title / maxLength
      Added value: +200
    • changedInput schema / required
      Previous value: -[
      -  "candidate",
      -  "company",
      -  "title",
      -  "salary",
      -  "startDate"
      -]New value: +[
      +  "candidate",
      +  "company",
      +  "title",
      +  "startDate"
      +]
  3. Changed5 schema fields changed
    • addedInput schema / properties / candidate / minLength
      Added value: +1
    • addedInput schema / properties / company / minLength
      Added value: +1
    • addedInput schema / properties / salary / minLength
      Added value: +1
    • addedInput schema / properties / startDate / minLength
      Added value: +1
    • addedInput schema / properties / title / minLength
      Added value: +1
  4. First observed

TDQS

C2.2/5.0
Behavior2/5

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

Annotations already cover the safety profile (readOnly, idempotent, closed-world, non-destructive), so the bar is lower, but the description adds nothing at all. It never mentions that the tool generates letter content, that includeDocx produces a Word file in result.docx, that past dates or low salary yield warnings/422s, or that defaults are filled in when fields are omitted.

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?

Four words is not conciseness but under-specification; there is no front-loaded statement of what the tool produces. Every necessary sentence is missing rather than every unnecessary sentence removed.

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?

For a 26-parameter tool with a nested contingencies object, five enums, internship/permanent branching, and no output schema, the description leaves out what the caller gets back (letter body, warnings, optional docx) and how the many optional fields change the output. The schema covers parameters, but the tool's core behavior and return shape are undocumented.

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 81% and the property descriptions are unusually rich (salary formats, 422 conditions, internship vs permanent branches, defaults), so the baseline of 3 applies. The description itself contributes zero parameter meaning, leaving the schema to carry the whole load.

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?

"Employment offer letter draft" only restates the tool name and title, adding no verb or scope beyond what the identifier already says. It does not distinguish this from near siblings such as business_cover_letter, business_nda_draft, or business_contract_pack, nor does it say whether it generates text, a file, or a structured object.

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

Usage Guidelines2/5

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

There is no when-to-use, when-not-to-use, or alternative-tool guidance of any kind. An agent must infer from the name alone that this is the letter-generation tool and not, say, a document analysis or storage tool.

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