Skip to main content
Glama
Sign In

PaperLesson — K-12 Vector Math Drills & Handwriting Worksheet Generator

by com.paperlesson
OverviewDiscussionsAdmin

Fractions on a Number Line Tick & Partition Calculator

generate_fraction_number_line_coordinates
Read-onlyIdempotent

Compute exact vector tick coordinates and benchmark labels for teaching proper fractions, improper fractions, and equivalent fractions on a 0-to-1 or 0-to-2 number line.

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": {
      "denominator": "<denominator>"
    },
    "name": "generate_fraction_number_line_coordinates"
  }
}

Input Schema

NameRequiredDescriptionDefault
denominatorYesFraction denominator (2, 3, 4, 5, 6, 8, 10, 12)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already establish that this is a read-only, idempotent, closed-world, non-destructive computation. The description adds useful scope by naming the output artifacts (tick coordinates and benchmark labels) and supported fraction types, but it does not describe coordinate formatting, label completeness, or return structure.

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?

The definition is a single tight sentence with the computational action and scope front-loaded. Every clause contributes to identifying what the tool produces and which fraction concepts it covers.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter read-only tool, the description covers the broad output and fraction types. However, it mentions '0-to-1 or 0-to-2 number line' without explaining how that range is selected, and there is no output schema explaining the exact return shape, leaving a meaningful completeness gap.

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?

There is only one parameter, denominator, and schema description coverage is 100%, including the allowed values. The description does not add semantics beyond what the schema already provides, so the baseline of 3 is appropriate.

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 uses a specific verb and resource: 'Compute exact vector tick coordinates and benchmark labels' for fractions on a number line. It also scopes the supported content (proper, improper, equivalent fractions) and line ranges, making the tool clearly distinguishable from sibling worksheet and lookup tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by 'for teaching proper fractions, improper fractions, and equivalent fractions,' but the description gives no explicit when-to-use or when-not-to-use guidance relative to alternatives. It provides context without routing rules or exclusions.

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

All PaperLesson — K-12 Vector Math Drills & Handwriting Worksheet Generator toolsInspect
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.

Resources