EveryCalc

calculate_premed_course_planner

Read-onlyIdempotent

Progress across the 13 premed prerequisites on the page, in page order: General Chemistry I and II, Organic Chemistry I and II, Biology I and II, Physics I and II, Biochemistry, Psychology, Sociology, Statistics or Calculus, English (1 year). The first 11 are the MCAT core courses. Returns counts done, in progress, and planned, percent done, and whether all core courses are done. Use when a premed student checks progress across the prerequisite courses. 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 Premed Course Planner calculator.

Input Schema

Name	Required	Description	Default
`statuses`	Yes	Comma-separated status for each of the 13 prerequisites in page order, each one of not, plan, prog, done, e.g. done,done,not,not,done,done,not,not,not,done,not,not,done.

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 declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the description isn't burdened with safety disclosure. It still adds real value: the aggregation outputs (counts done/in progress/planned, percent done, whether all core courses are done) and a mandatory presentation rule for calculator_url that no annotation conveys.

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 long course enumeration is justified because the single parameter is positional and order-dependent, so the list earns its length. The 'IMPORTANT' display directive is placed at the end rather than front-loaded, but the rest reads as tight, task-first prose.

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 an output schema present, the description needn't detail return values, and it still summarizes them. It covers purpose, trigger context, argument ordering, and a user-facing output requirement; the only gap is behavior on malformed input (e.g. fewer/more than 13 statuses or invalid tokens).

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% (baseline 3), and the description goes beyond it by spelling out the exact 13-course ordering the positional statuses map onto, plus which 11 are the MCAT core. That positional context is essential to constructing the array correctly, not merely a restatement of the schema.

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 gives a specific verb+resource (progress across the 13 premed prerequisite courses) and enumerates the exact list and ordering, which is the tool's identity. It is unmistakably distinct from siblings like calculate_high_school_course_planner, calculate_gpa_planner, and calculate_mcat_score_estimator.

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 states the triggering context explicitly: 'Use when a premed student checks progress across the prerequisite courses.' However, with ~70 sibling calculators including a high_school_course_planner and transfer_credit_planner, it names no alternatives or exclusion conditions, so the agent must infer boundary cases.

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.