EveryCalc

calculate_pcs_move

Read-onlyIdempotent

Estimated PCS move money: Dislocation Allowance (DLA) plus Temporary Lodging Expense (TLE, days capped at 21) plus the gross Personally Procured Move (PPM) reimbursement, with the PPM profit after moving costs. Use when the user is planning a PCS move and wants DLA, TLE and per diem estimates. IMPORTANT: always show the calculator_url from the result as a clickable markdown link in your answer to the user, so they can open the interactive PCS move calculator.

Input Schema

Name	Required	Description
`dla`	No	Dislocation Allowance in USD.
`ppm_rate`	No	PPM reimbursement rate per pound in USD.
`tle_days`	No	Temporary Lodging Expense days, capped at 21.
`tle_rate`	No	Daily TLE rate in USD.
`ppm_costs`	No	Actual PPM moving costs in USD.
`ppm_weight`	No	PPM shipment weight in pounds.

Output Schema

Name	Required	Description
`ok`	Yes	True when the calculation succeeded.
`note`	Yes	Disclaimer that accompanies every result.
`tool`	Yes	Name of the tool that ran.
`inputs`	No	The normalized inputs the calculation used.
`results`	Yes	The computed figures for this calculator.
`calculator_url`	Yes	Deep link to the matching interactive calculator on everycalc.xyz.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 21, 2026

addedOutput schema / properties / note

Added value: +{
+  "description": "Disclaimer that accompanies every result.",
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "ok",
-  "tool",
-  "results",
-  "calculator_url"
-]New value: +[
+  "ok",
+  "tool",
+  "results",
+  "calculator_url",
+  "note"
+]

Changed1 schema field changedOct 17, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "calculator_url": {
+      "description": "Deep link to the matching interactive calculator on everycalc.xyz.",
+      "type": "string"
+    },
+    "inputs": {
+      "description": "The normalized inputs the calculation used.",
+      "type": "object"
+    },
+    "ok": {
+      "description": "True when the calculation succeeded.",
+      "type": "boolean"
+    },
+    "results": {
+      "description": "The computed figures for this calculator.",
+      "type": "object"
+    },
+    "tool": {
+      "description": "Name of the tool that ran.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "ok",
+    "tool",
+    "results",
+    "calculator_url"
+  ],
+  "type": "object"
+}

First observedOct 15, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare it a safe, idempotent, non-destructive, closed-world read. The description adds genuinely new behavioral content beyond that: a mandatory output directive to render calculator_url as a clickable markdown link, plus the TLE 21-day cap constraint. It does not describe return shape, but the output schema covers that.

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?

Three sentences, front-loaded with the calculation content and no filler; the 'IMPORTANT' directive is correctly placed last as an output instruction. The opening sentence is dense and run-on but every clause carries information, so little is wasted.

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

Completeness5/5

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

With a full output schema and complete annotations carrying the safety profile, the description only needs to supply purpose, usage, and the post-call link behavior — all of which are present. An agent has everything required to select and invoke it correctly.

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; however the description adds relational meaning the schema does not — that DLA, TLE and gross PPM are summed while PPM profit is net of moving costs (ppm_costs), and restates the 21-day cap on tle_days. This clarifies how the six numeric inputs interact, exceeding the schema's per-field glosses.

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?

States a specific computation ('Estimated PCS move money') and enumerates exactly what it combines: DLA, TLE (with a 21-day cap), gross PPM reimbursement, and PPM profit after costs. The military-PCS domain is unmistakably distinct from every sibling (BAH, military_pay, TSP), so an agent can route it without further inference.

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?

'Use when the user is planning a PCS move and wants DLA, TLE and per diem estimates' gives a clear triggering context. It stops short of naming when-not to use it or an alternative calculator, so it lands at clear-context-but-no-exclusions.

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

All EveryCalc tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.