Skip to main content
Glama

Custom Solutions

1031 exchange deadlines

compute_1031_deadlines
Read-onlyIdempotent

The two deadlines of a 1031 like-kind exchange from the date the relinquished property was transferred: day 45 to identify replacement property, and the end of the exchange period, which is the earlier of day 180 or the due date (with extensions) of the tax return for the year of the transfer. Calendar arithmetic is where these go wrong: day 1 is the day after the transfer, a deadline on a weekend or holiday stays where it falls, and a late-year transfer can lose weeks to an unextended return. Send transfer_date as YYYY-MM-DD and, when day 180 may fall after the return is due, return_due_date; without it, the answer names both candidate dates and the missing input.

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": {
      "transfer_date": "<transfer_date>"
    },
    "name": "compute_1031_deadlines"
  }
}

Input Schema

NameRequiredDescriptionDefault
transfer_dateYesDate the relinquished property was transferred, YYYY-MM-DD, e.g. 2026-11-19
return_due_dateNoDue date, with extensions, of the tax return for the year of the transfer, YYYY-MM-DD, e.g. 2027-10-15

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already establish this as a read-only, idempotent, non-destructive, closed-world calculation, so the safety profile is covered. The description adds useful behavioral detail, such as the fallback behavior when return_due_date is omitted, but it doesn't describe the shape of the returned dates or units beyond that fallback. The added value is real but modest against an already-complete annotation set.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the two deadlines before the arithmetic caveats and the input instructions, and every sentence carries information. The opening sentence is long and packs both deadlines plus the extension rule into one clause chain, which slightly slows parsing but is not wasteful.

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?

With no output schema, the description must convey what comes back, and it does: the two dates, or both candidate dates plus a note about the missing input. Combined with the arithmetic caveats, an agent can call this correctly and interpret the result, though the exact return format remains implicit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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, but the description adds meaning the schema does not: day 1 is the day after transfer, weekend or holiday deadlines do not shift, and a late-year transfer can lose weeks to an unextended return. These conventions explain why return_due_date matters and how to pick it, which is genuine semantic lift beyond the field descriptions.

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 opens with a specific verb and resource: it computes the two 1031 like-kind exchange deadlines (day 45 identification and the exchange period end). Both deadlines are defined precisely, so an agent knows exactly what this tool returns and can distinguish it from the other compute_* siblings, which cover unrelated financial calculations.

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 conditional rule for the optional input: supply return_due_date when day 180 may fall after the return due date, and otherwise the tool still returns both candidate dates. There is no explicit when-not-to-use or named alternative, but the sibling set contains no overlapping tool, so the gap is minor.

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