Homeschool Tools

search_offerings

Read-onlyDestructive

Look up specific homeschool offerings by name in the Homeschool Tools database (e.g., to check whether a curriculum the user mentioned is covered, or to get its slug for other tools). Returns name, slug, and a one-line summary per match. Do not use this for general recommendations (use find_curriculum), and do not use it for lesson planning, tutoring, or non-curriculum questions.

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": {
      "query": "<query>"
    },
    "name": "search_offerings"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes	Offering or publisher name to look up, e.g. 'Sonlight' or 'Beast Academy'.

Output Schema

Name	Required	Description	Default
`note`	No
`query`	Yes
`results`	Yes
`result_count`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 6, 2026

TDQS

A3.8/5.0

Behavior1/5

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

The annotation destructiveHint=true directly contradicts the description, which says the tool only looks up offerings and returns name, slug, and summary. The readOnlyHint=true supports the description, but the destructive hint creates a serious inconsistency that an agent cannot resolve confidently. Per the rubric, a description that contradicts annotations receives a score of 1.

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 description is three sentences with no filler. The main purpose is front-loaded, return values are summarized, and exclusions with alternatives are stated directly. Every sentence contributes to correct tool selection and invocation.

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 one-parameter lookup tool with an output schema, the description covers purpose, return contents, and exclusions thoroughly. The only notable gap is the contradictory destructiveHint annotation, which creates avoidable confusion despite the description itself being complete.

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, query, and the schema already documents it at 100% coverage, including examples like 'Sonlight' or 'Beast Academy.' The description reinforces the intended use by framing the query as a specific offering or publisher name, but it does not add substantial semantic detail beyond the schema.

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: 'Look up specific homeschool offerings by name in the Homeschool Tools database.' It also gives concrete examples of when to use it, such as checking coverage or getting a slug, and clearly differentiates it from find_curriculum and other general-purpose tools.

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

Usage Guidelines5/5

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

The description explicitly states when to use the tool ('to check whether a curriculum the user mentioned is covered, or to get its slug') and when not to use it ('Do not use this for general recommendations, lesson planning, tutoring, or non-curriculum questions'). It even names the alternative tool, find_curriculum, making the routing clear.

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?