Skip to main content
Glama

Write a will

create_will
Read-onlyIdempotent

Draft a complete U.S. last will and testament, optionally with charitable gifts to causes the person chooses. For people who want to make, write or update a will. Every name and fact in the input comes from the person. Returns the will text, a state-specific signing checklist, a plain-English summary of who inherits, and warnings to resolve before signing. Not legal advice; wills are not produced for Louisiana or North Carolina residents (gift wording is returned instead).

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": {
      "person": "<person>"
    },
    "name": "create_will"
  }
}

Input Schema

NameRequiredDescriptionDefault
fundNoOnly for giving_method named_fund: a foundation-style named fund that keeps giving.
causesNoCauses that receive the charitable gift, with each one's share. Use list_causes for the built-in causes, or describe your own.
familyNoFamily and who inherits the part of the estate that does not go to causes.
personYesThe person making the plan.
backstopNoIf no one named in the will survives, give everything to the causes instead of to unnamed relatives or the state. Off unless the person explicitly wants it.
executorNoFull name of the executor (personal representative).
guardianNoGuardian for minor children.
giving_methodNoresearch_guided: each cause's share goes to Systemic Altruism Foundation's (EIN 87-2067921) Cause Fund for that cause, which grants it to effective charities working on it, guided by MyLastWill.org research (default). named_charities: give to the specific charities listed under each cause. named_fund: create a named legacy fund (see fund).
backup_executorNo
backup_guardianNo
estate_estimateNoRough value in USD of property passing under the will (exclude retirement accounts, life insurance and anything with a named beneficiary or joint owner). Used only for dollar estimates.
has_living_trustNoTrue if the person has a revocable living trust (a new will may affect it).
charitable_timingNoFor a married person leaving the rest to their spouse: at_my_death pays the charitable share at the person's death even if the spouse survives; after_spouse pays it only if the spouse doesn't survive them, so a surviving spouse receives everything. Ask; don't assume. Defaults to at_my_death.
minor_money_managerNoPerson to manage property that minor children inherit (optional).
charitable_share_percentNoPercentage of the estate that goes to causes. 0 for none.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / family / properties / children / description
      Previous value: -"Full names of all children, including adopted children. Use [] if none."New value: +"Full names of all of the person's own children, by birth or adoption, including any they want to leave nothing to. Not stepchildren unless adopted. To leave a child out, use plan named_people and give that child percent 0. Use [] if none."
    • changedInput schema / properties / family / properties / people / description
      Previous value: -"For plan named_people: who inherits and each person's percentage of the family share."New value: +"For plan named_people: who inherits and each person's percentage of the family share. percent is a number from 0 to 100; a person given 0 receives nothing. If no one has a percent, they share equally. At most 20 people."
    • addedInput schema / properties / family / properties / people / items / properties / percent / maximum
      Added value: +100
    • addedInput schema / properties / family / properties / people / items / properties / percent / minimum
      Added value: +0
    • addedInput schema / properties / family / properties / people / maxItems
      Added value: +20
  2. Changed1 schema field changed
    • addedInput schema / properties / charitable_timing
      Added value: +{
      +  "description": "For a married person leaving the rest to their spouse: at_my_death pays the charitable share at the person's death even if the spouse survives; after_spouse pays it only if the spouse doesn't survive them, so a surviving spouse receives everything. Ask; don't assume. Defaults to at_my_death.",
      +  "enum": [
      +    "at_my_death",
      +    "after_spouse"
      +  ],
      +  "type": "string"
      +}
  3. Changed1 schema field changed
    • changedInput schema / properties / giving_method / description
      Previous value: -"research_guided: the executor gives each cause's share to effective charities working on it, guided by MyLastWill.org research (default). named_charities: give to the specific charities listed under each cause. named_fund: create a named legacy fund (see fund)."New value: +"research_guided: each cause's share goes to Systemic Altruism Foundation's (EIN 87-2067921) Cause Fund for that cause, which grants it to effective charities working on it, guided by MyLastWill.org research (default). named_charities: give to the specific charities listed under each cause. named_fund: create a named legacy fund (see fund)."
  4. First observed

TDQS

A4/5.0
Behavior4/5

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

With no output schema, the description carries the return-value burden and does it well: will text, state-specific signing checklist, plain-English inheritance summary, and warnings to resolve before signing. It also sets expectations with "Not legal advice" and the LA/NC fallback. It doesn't say whether anything is persisted, though readOnlyHint/idempotentHint annotations cover the safety profile.

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?

Four sentences, front-loaded with the verb and artifact, then audience, then outputs, then caveats. No redundant restatement of the name or title, and every sentence carries distinct information.

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

Completeness4/5

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

For a 15-parameter tool with nested objects and no output schema, the description covers purpose, audience, outputs, and jurisdictional limits. Minor gap: it doesn't hint at the sequencing with list_causes or the state-requirements sibling, though the schema itself points to list_causes.

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 87%, so the schema already explains nearly every parameter, including enums like giving_method and charitable_timing. The description adds only a light constraint ("Every name and fact in the input comes from the person") and the optional charitable-gift framing, so baseline 3 applies.

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

Purpose4/5

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

States a specific verb and artifact: "Draft a complete U.S. last will and testament", plus the optional charitable-gift variant. It is clearly distinguishable from the named siblings like add_charity_to_existing_will (this one drafts the whole document) and get_bequest_language (this returns a full will, not clause text), though it doesn't name those alternatives explicitly.

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?

"For people who want to make, write or update a will" gives the primary use case, and the description supplies a clear exclusion: no wills for Louisiana or North Carolina residents, gift wording is returned instead. No guidance on when to prefer add_charity_to_existing_will or get_state_will_requirements first, which keeps it below a 5.

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