Skip to main content
Glama
freelance-tax-mcp

freelance-tax-mcp

IRS mileage deduction

mileage

Calculate 2026 standard vehicle tax deductions by trip date, applying 72.5¢ and 76¢ rates to trip logs or split totals, including parking and tolls.

Instructions

Standard mileage deduction priced by the date each mile was driven (2026 business rate 72.5 cents Jan-Jun, 76 cents from Jul 1). Pass trips, or 2026 split totals such as business_jan_jun and business_jul_dec.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "mileage"
  }
}

Input Schema

NameRequiredDescriptionDefault
tripsNoTrip log
parking_tollsNoBusiness parking and tolls, added on top
moving_jan_junNo
moving_jul_decNo
charity_jan_junNo
charity_jul_decNo
medical_jan_junNo
medical_jul_decNo
business_jan_junNo
business_jul_decNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the date-based business rate schedule, but it does not state that this is a read-only calculation, how trips and split totals interact, or what the result looks like.

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 tightly written sentences with no wasted text. It front-loads the deduction and rate logic, then immediately gives the input modes.

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 10-parameter calculation tool with no output schema and no annotations, the description is incomplete. It does not explain most split-total parameters, the non-business mileage categories, mutual exclusivity between trips and totals, or the tool's return behavior.

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

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 20%, so the description needs to compensate for many undocumented parameters. It mentions trips and business_jan_jun/business_jul_dec, but omits parking_tolls, the moving/charity/medical split totals, purpose enum behavior, and the date format requirements.

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 clearly identifies a standard mileage deduction calculated by trip date, with 2026 business rates and date-based pricing. It is specific about the resource and calculation, but it does not explicitly differentiate itself from sibling tools such as mileage_rates or estimate.

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

Usage Guidelines3/5

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

The description says to pass trips or 2026 split totals such as business_jan_jun and business_jul_dec, which gives input-selection guidance. However, it does not explain when to use this tool versus mileage_rates or estimate, nor when trips should be preferred over split totals.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.