EveryCalc

calculate_mcat_score_estimator

Read-onlyIdempotent

Estimated MCAT section scores on the 118 to 132 scale: 118 plus the fraction correct times 14, per section, plus the total on the 472 to 528 scale. Use when the user estimates MCAT section scores from practice results. 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 MCAT Score Estimator calculator.

Input Schema

Name	Required	Description
`section1_total`	Yes	Total section 1 questions.
`section2_total`	Yes	Total section 2 questions.
`section3_total`	Yes	Total section 3 questions.
`section4_total`	Yes	Total section 4 questions.
`section1_correct`	Yes	Section 1 questions answered correctly.
`section2_correct`	Yes	Section 2 questions answered correctly.
`section3_correct`	Yes	Section 3 questions answered correctly.
`section4_correct`	Yes	Section 4 questions answered correctly.

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.3/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, closed-world), so the description's added value is the disclosure of the exact scoring formula and the mandatory follow-up action: surface the returned calculator_url as a clickable markdown link. That output-handling requirement is real behavioral context not available from annotations or schema.

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?

Front-loaded with the computation and the triggering condition, then the link-rendering requirement. Three sentences, each doing work. The IMPORTANT clause is slightly verbose but is a hard requirement, so it earns its space.

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?

An output schema exists, so the description needn't explain return values, and it correctly focuses on the one output behavior that matters (showing calculator_url). For an eight-parameter, fully documented, annotation-covered calculator, this is complete; only the sibling-routing guidance is thin.

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 eight parameters are already documented (correct counts and totals per section). The description adds meaning beyond the schema by explaining what the inputs are used for – fraction correct scaled onto 118–132 per section – which tells the agent the counts must be internally consistent rather than arbitrary numbers.

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 names a specific verb+resource (estimate MCAT section scores) and even states the scoring model: 118 + fraction correct × 14 per section, plus the 472–528 total. This cleanly separates it from siblings like calculate_lsat_score_estimator and calculate_gre_score_estimator, which share the same 'estimate a test score' pattern.

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 estimates MCAT section scores from practice results" gives a clear triggering context, and the four-section input shape implies it needs all four sections at once. It does not, however, explicitly rule out or route to the other score estimators (SAT, ACT, PSAT, LSAT, GRE) when a user's request is ambiguous.

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.