Skip to main content
Glama

EveryCalc

calculate_graduate_school_roi

Read-onlyIdempotent

Annual salary premium after a graduate degree, break-even years on the total cost, and lifetime net over the career years, using the page formulas. Use when the user weighs graduate school cost against the salary premium it brings. 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 Graduate School ROI calculator.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "total_cost": "<total_cost>",
      "current_salary": "<current_salary>",
      "post_degree_salary": "<post_degree_salary>"
    },
    "name": "calculate_graduate_school_roi"
  }
}

Input Schema

NameRequiredDescriptionDefault
total_costYesTotal graduate degree cost in USD.
career_yearsNoCareer years after graduation; default 20.
current_salaryYesCurrent yearly salary in USD.
post_degree_salaryYesExpected yearly salary after the degree in USD.

Output Schema

NameRequiredDescriptionDefault
okYesTrue when the calculation succeeded.
noteYesDisclaimer that accompanies every result.
toolYesName of the tool that ran.
inputsNoThe normalized inputs the calculation used.
resultsYesThe computed figures for this calculator.
calculator_urlYesDeep link to the matching interactive calculator on everycalc.xyz.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • 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"
      +]
  2. Changed1 schema field changed
    • 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"
      +}
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety burden is lifted. The description adds real operational context by disclosing that the result carries a calculator_url that must be surfaced as a clickable markdown link, and it names the computed outputs so the agent knows what comes back.

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 output summary before the usage trigger and the link instruction. The 'IMPORTANT' clause is justified because it changes agent behavior, but the opening sentence is densely packed and repeats output details the output schema already carries.

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 return values need little explanation, and the description still covers the trigger condition plus the one post-processing requirement (link the calculator_url) that the schema cannot express. Nothing essential to a correct call 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 coverage is 100% and every parameter (total_cost, career_years, current_salary, post_degree_salary) is documented in-schema with units and the career_years default. The description only gestures at 'the total cost' and 'the career years', adding no format or unit detail beyond what the schema already provides, so the baseline 3 applies.

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 (calculate) plus the exact outputs produced: annual salary premium, break-even years on total cost, and lifetime net over career years. The 'graduate degree' scope clearly separates it from the undergrad-oriented calculate_college_roi and calculate_college_major_roi siblings.

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 weighs graduate school cost against the salary premium it brings" gives a clear triggering context, which is uncommon among these calculator siblings. It does not, however, name a specific alternative tool or state when-not to use it.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.