Skip to main content
Glama

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

List All K-12 Classroom Tools

list_classroom_tools
Read-onlyIdempotent

List all 47 interactive classroom tools in Birkan Yavuz's catalog. Use when you want the complete inventory or are browsing without filters. Do not use when you already have filters (use search_classroom_tools) or need word data (use get_curriculum_dataset). Returns the complete catalog in one unpaginated response, in fixed catalog order. 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": "list_classroom_tools"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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. First observed

TDQS

A4.7/5.0
Behavior4/5

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

The annotations already declare read-only, idempotent, non-destructive, and closed-world behavior. The description adds useful context beyond that: the response is unpaginated, returned in fixed catalog order, and requires no authentication. It does not discuss rate limits or error behavior, but the key behavioral traits are covered.

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 four tight sentences with no wasted wording. The primary purpose and usage conditions are front-loaded, followed by return behavior and authentication context.

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?

Given the tool's simplicity, zero parameters, rich annotations, and existing output schema, the description provides everything an agent needs to select and invoke it correctly. It covers scope, alternatives, response shape, ordering, and authentication.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so there is no parameter semantics to explain. The baseline for a no-parameter tool is 4, and the description does not need to compensate for missing schema coverage.

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 states a specific verb and resource: listing all 47 interactive classroom tools in the catalog. It also distinguishes this tool from search_classroom_tools and get_curriculum_dataset, so an agent can identify its role 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 explicitly says when to use the tool (complete inventory or browsing without filters) and when not to use it (when filters are needed, use search_classroom_tools; when word data is needed, use get_curriculum_dataset). The alternatives are named with clear selection conditions.

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.