Homeschool Tools

compare_offerings

Read-onlyDestructive

Use this when a user wants to compare 2-3 specific homeschool curricula side by side (e.g., 'Sonlight vs My Father's World'). Returns full detail for each offering so you can contrast approach, price, worldview, parent time, and reviewer consensus. Pass slugs when known, names otherwise.

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": {
      "slugs": "<slugs>"
    },
    "name": "compare_offerings"
  }
}

Input Schema

Name	Required	Description	Default
`slugs`	Yes	2-3 offering slugs (preferred) or names, e.g. ["sonlight","my-fathers-world"].

Output Schema

Name	Required	Description	Default
`not_found`	No
`offerings`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 6, 2026

TDQS

B3.4/5.0

Behavior1/5

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

The description presents the operation as purely read-only ('Returns full detail for each offering'), but the annotations include destructiveHint=true. That directly contradicts the non-destructive compare/return behavior, and the description never resolves the conflict. This is an annotation contradiction.

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 are front-loaded with the use case, a useful example, and a parameter hint. Concise and readable, though the final sentence partly duplicates the schema description of the slugs parameter.

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?

With one parameter and an output schema, the description is nearly sufficient, but it fails to address the obvious conflict between readOnlyHint=true and destructiveHint=true. It also does not explicitly direct the agent to sibling tools for single-detail or search intents, which would improve completeness.

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?

The schema already documents the parameter with 100% coverage, including '2-3 offering slugs (preferred) or names.' The description's 'Pass slugs when known, names otherwise' repeats that guidance without adding new meaning, so the baseline score of 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 opens with a clear trigger and resource: 'compare 2-3 specific homeschool curricula side by side,' with a concrete example ('Sonlight vs My Father's World'). It is easy to distinguish from a search or single-detail tool: this is explicitly a bounded, side-by-side comparison.

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 this when a user wants to compare 2-3 specific homeschool curricula' is an explicit usage condition. It does not explicitly name alternatives such as get_offering_detail or search_offerings, nor state when not to use this tool, so it falls just short of full routing guidance.

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

All Homeschool Tools 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.

Resources

Need Help?