EveryCalc

calculate_student_budget

Read-onlyIdempotent

Monthly budget from job, parent, and aid income against rent, food, books, transport, and fun spending. Returns total income, total expenses, the balance, and the largest category with its share of expenses. Use when a student builds a monthly budget from income against rent, food, books, transport and fun spending. 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 Student Budget calculator.

Input Schema

Name	Required	Description
`fun`	Yes	Monthly fun and entertainment spending in USD.
`food`	Yes	Monthly food spending in USD.
`rent`	Yes	Monthly rent in USD.
`books`	Yes	Monthly books and supplies spending in USD.
`transport`	Yes	Monthly transport spending in USD.
`aid_income`	Yes	Monthly financial aid income in USD.
`job_income`	Yes	Monthly job income in USD.
`parent_contribution`	Yes	Monthly contribution from parents in USD.

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

A3.8/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the bar is lower, and the description still adds real behavior: the exact returned figures (totals, balance, largest category share) and a mandatory instruction to render calculator_url as a clickable markdown link. That post-call obligation is useful disclosure beyond the structured fields.

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

Conciseness3/5

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

The content is front-loaded and scannable, but sentence 3 restates sentence 1 almost verbatim, and the return-value sentence duplicates what the output schema already carries. One redundant sentence passed without being trimmed.

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 an eight-parameter deterministic calculator, the description is self-sufficient: it covers inputs, the shape of the result, and the required output formatting. An output schema exists, so return values need not be detailed further, and annotations cover the safety profile; nothing essential is missing.

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 explains all eight parameters, giving a baseline of 3. The description's grouping of the parameters into income versus expense categories adds a small amount of meaning the schema does not state explicitly, but that is the extent of the added value.

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 names a specific verb-and-resource pair ('Monthly budget') and enumerates the exact income sources (job, parent, aid) and expense categories (rent, food, books, transport, fun), so an agent can tell it apart from neighbors like calculate_affordability or calculate_dorm_vs_apartment. It does not name a sibling explicitly, keeping it short of a 5.

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 a student builds a monthly budget from income against rent, food, books, transport and fun spending' gives a clear trigger condition, and the IMPORTANT line adds a required follow-up action. There are no when-not conditions or named alternatives, so it stops short of a 5.

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.