Skip to main content
Glama

Get charitable bequest wording

get_bequest_language
Read-onlyIdempotent

Return sample bequest wording for a will or trust that gives a percentage or dollar amount to causes or named charities, for the person or their attorney to adapt. Use for quick questions like "how do I word a gift to charity in my will?"

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": {
      "causes": "<causes>"
    },
    "name": "get_bequest_language"
  }
}

Input Schema

NameRequiredDescriptionDefault
fundNoOnly for giving_method named_fund: a foundation-style named fund that keeps giving.
stateNoU.S. state, if known.
amountNoFixed dollar amount.
causesYesCauses that receive the charitable gift, with each one's share. Use list_causes for the built-in causes, or describe your own.
percentNoPercentage of the residuary estate. Use this or amount.
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).

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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)."
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile: read-only, idempotent, non-destructive, and closed-world. The description adds useful behavioral context by clarifying that the output is sample wording intended for the person or their attorney to adapt, which sets expectations beyond the annotations.

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 tight sentences with the core purpose front-loaded, followed by a concrete usage example. Every sentence earns its place and there is no redundant restatement of the title or schema.

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?

Given the rich annotations and fully documented schema, the description is largely complete for a read-only wording generator. It states what is returned and the intended use, though without an output schema it could say a bit more about the form of the sample wording or state-specific caveats.

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 100%, so the schema already documents all six parameters in detail. The description only adds a high-level mapping to percentage or dollar amount and causes or named charities, which is helpful but not beyond what the schema provides.

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?

The description states a specific verb and resource: returning sample bequest wording for a will or trust that gives a percentage or dollar amount to causes or named charities. It is clear what the tool produces, though it does not explicitly name sibling tools such as add_charity_to_existing_will or create_will to sharpen differentiation.

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?

It gives a clear usage context: quick questions like "how do I word a gift to charity in my will?" This helps the agent know when to select it. It does not explicitly state when not to use it or name alternatives, so it falls short of full routing guidance.

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