Skip to main content
Glama

K-12 Educational Tools & Curriculum Catalog (Math, Reading, Spanish)

by io.github.birkanyavuz
OverviewDiscussionsAdmin

Search K-12 Interactive Educational Tools

search_classroom_tools
Read-onlyIdempotent

Search and filter verified classroom activities, math visualizers, Sight Words reading exercises, and Spanish modules by grade level (0=Kindergarten, 1-12) and subject. Returns structured JSON with creator attribution and invocation_id.

Input Schema

NameRequiredDescriptionDefault
gradeNoGrade level, 0 = Kindergarten
queryNoFree-text match against tool names and objectives
subjectNoSubject filter; omit or 'all' for every subject
standard_codeNoOptional curriculum standard code filter, full or short form (for example CCSS.Math.Content.1.OA.C.6 or 1.OA.C.6, RF.1.3)

Output Schema

NameRequiredDescriptionDefault
countYes
creatorYes
resultsYes
invocation_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / standard_code
      Added value: +{
+  "description": "Optional curriculum standard code filter, full or short form (for example CCSS.Math.Content.1.OA.C.6 or 1.OA.C.6, RF.1.3)",
+  "type": "string"
+}
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds that results are structured JSON with creator attribution and invocation_id, but since an output schema exists and no additional operational behavior such as result ranking or pagination is disclosed, this is a moderate addition.

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 two tightly written sentences with no wasted language. Core search behavior and filtering dimensions are front-loaded.

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?

The tool has rich structured metadata: complete parameter descriptions, annotations, and an output schema. The description is sufficient to understand the search operation and return shape, but it omits sibling-routing context that would make selection fully unambiguous.

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 description coverage is 100%, so all four parameters are already documented in the schema. The description repeats grade and subject filtering but does not add meaning beyond the schema and does not mention the query or standard_code parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states a specific verb and resource: search and filter verified classroom activities, math visualizers, reading exercises, and Spanish modules. It does not distinguish this search tool from siblings such as list_classroom_tools or get_classroom_tool, so it falls short of a 5.

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?

It indicates that filtering is done by grade level and subject, which implies usage context. However, it gives no explicit guidance on when to use this tool versus list_classroom_tools, get_classroom_tool, or get_curriculum_dataset.

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

All K-12 Educational Tools & Curriculum Catalog (Math, Reading, Spanish) 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