EveryCalc

calculate_lsat_score_estimator

Read-onlyIdempotent

Estimated LSAT scaled score on the 120 to 180 scale: 120 plus the overall fraction correct across the three sections times 60, with accuracy and the page score band. Use when the user estimates an LSAT scaled score from practice section 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 LSAT 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.
`section1_correct`	Yes	Section 1 questions answered correctly.
`section2_correct`	Yes	Section 2 questions answered correctly.
`section3_correct`	Yes	Section 3 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.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint true, openWorldHint/destructiveHint false, so the safety profile is covered. The description adds genuine behavioral context beyond that: the scoring formula the tool applies, and a mandatory post-call behavior (always surface calculator_url as a clickable markdown link). It does not discuss rounding, precision or edge cases of the estimate.

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?

Definition and formula are front-loaded before the usage sentence and the trailing IMPORTANT instruction, and every sentence carries a distinct job. The formula sentence is dense (e.g. 'the page score band' is unexplained jargon), which costs a point.

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?

An output schema exists, so return values need not be described, and the description still adds the scale, the formula, and the required downstream handling of calculator_url. Nothing an agent needs to invoke this correctly and present the result is missing.

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% with all six section_correct/section_total parameters individually documented, so the baseline is 3. The description earns above baseline by explaining how those inputs combine ('overall fraction correct across the three sections times 60'), giving the aggregation semantics the schema alone does not.

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 states a specific resource (LSAT scaled score on the 120–180 scale) and the exact computation ('120 plus the overall fraction correct across the three sections times 60'), which makes it unmistakable against the many sibling score estimators (calculate_act_score, calculate_sat_score, calculate_gre_score_estimator, calculate_mcat_score_estimator). An agent can tell what this tool produces without opening the schema.

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 an LSAT scaled score from practice section results' gives a clear triggering condition, and the three-section input shape implicitly excludes single-score or curve-lookup tools. No explicit alternatives or when-not-to-use cases are named, so it falls 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.