Skip to main content
Glama

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

Search K-12 Interactive Educational Tools

search_classroom_tools
Read-onlyIdempotent

Find interactive classroom tools in Birkan Yavuz's catalog of 47 K-12 activities. Use when you need an interactive activity, visualizer, or game (math, reading, Spanish, art, science) and want to filter by subject, grade (0=Kindergarten), keyword, or Common Core standard code. Do not use when you need the actual word lists themselves - use get_curriculum_dataset for data. Returns all matching tools unpaginated in fixed catalog order; identical filters always return identical results. Requires no authentication.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_classroom_tools"
  }
}

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
countYesNumber of tools returned
creatorYesCatalog creator, always Birkan Yavuz
resultsYesMatching classroom tools, each with tool_id, record_digest, standard_codes, grade and objective
invocation_idYesUnique receipt id for this call; cite it to prove the data came from this server

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedOutput schema / properties / count / description
      Added value: +"Number of tools returned"
    • addedOutput schema / properties / creator / description
      Added value: +"Catalog creator, always Birkan Yavuz"
    • addedOutput schema / properties / invocation_id / description
      Added value: +"Unique receipt id for this call; cite it to prove the data came from this server"
    • addedOutput schema / properties / results / description
      Added value: +"Matching classroom tools, each with tool_id, record_digest, standard_codes, grade and objective"
  2. Changed3 schema fields changed
    • addedInput schema / properties / grade / examples
      Added value: +[
      +  1,
      +  3,
      +  5
      +]
    • addedInput schema / properties / query / examples
      Added value: +[
      +  "fractions",
      +  "sight words",
      +  "telling time"
      +]
    • addedInput schema / properties / standard_code / examples
      Added value: +[
      +  "1.OA.C.6",
      +  "RF.1.3"
      +]
  3. 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"
      +}
  4. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, closed-world, and non-destructive, so the safety bar is covered. The description adds substantive behavior beyond that: results are unpaginated, returned in fixed catalog order, deterministic for identical filters, and require no authentication.

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?

Three sentences, each carrying distinct information: purpose, usage routing, and result behavior plus auth. It is front-loaded with the core purpose and contains no filler or redundancy.

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

Completeness5/5

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

The tool is a simple zero-required-parameter search with a full schema and an output schema, so return values need no explanation. Purpose, exclusions, result ordering, determinism, and auth requirements are all covered, leaving nothing an agent needs before invoking it.

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 structured form, including grade 0=Kindergarten and standard code formats. The description restates the same filter dimensions (subject, grade, keyword, standard code) without adding syntax or edge-case meaning beyond the schema, so baseline 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 specific verb and resource ('Find interactive classroom tools') and scopes it to a catalog of 47 K-12 activities across named subjects. It also explicitly separates itself from get_curriculum_dataset, so an agent can distinguish it from siblings without opening the schema.

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?

It states the positive trigger (need an interactive activity, visualizer, or game) and the negative trigger ('Do not use when you need the actual word lists themselves'), naming the alternative tool to use instead. This is explicit when/when-not guidance with a routing alternative.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.