API Hub MCP — 337+ Tools

slope_calc

Calculate the slope, intercept, and equation of a line from two points. Input x and y coordinates to get the linear relationship.

Instructions

Calculate the slope, intercept, and equation of a line between two points.

Parameters:
    x1 — X coordinate of first point.
    y1 — Y coordinate of first point.
    x2 — X coordinate of second point.
    y2 — Y coordinate of second point.

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": {
      "x1": "<x1>",
      "y1": "<y1>",
      "x2": "<x2>",
      "y2": "<y2>"
    },
    "name": "slope_calc"
  }
}

Input Schema

Name	Required	Description	Default
`x1`	Yes
`y1`	Yes
`x2`	Yes
`y2`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.4.1Jun 22, 2026

TDQS

A4.2/5.0

Behavior3/5

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

No annotations provided, so description carries full burden. It describes the calculation but lacks warnings about edge cases (e.g., vertical line when x1=x2) or return format. Basic but adequate for a pure calculation tool.

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

Conciseness5/5

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

Two sentences plus a clean list. Every sentence adds value, no redundancy. The structure is easy to scan and well-organized.

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 a simple tool with 4 required parameters and no nested objects, the description covers the main functionality. Missing edge case handling but acceptable. Output schema may define return values, so completeness is adequate.

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 descriptions are missing (0% coverage), so the description provides all parameter meaning. Each parameter is explained with coordinate roles, adding significant value beyond the schema titles.

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 clearly states it calculates slope, intercept, and equation from two points. Uses specific verb 'calculate' and resource 'slope, intercept, equation'. No sibling tools overlap, so no differentiation needed.

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?

The purpose is clear and implies usage context. No explicit when-to-use or alternatives are needed because no sibling tool performs the same function. However, it could be improved by adding explicit guidance.

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

Deploy Server