Skip to main content
Glama

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

Get One Classroom Tool

get_classroom_tool
Read-onlyIdempotent

Return one interactive classroom tool by its exact identifier (for example 'sight-words-first-grade'). Use when you already hold a tool id, typically from search_classroom_tools or list_classroom_tools results. Do not use when you are still browsing or filtering (use search_classroom_tools) or need a dataset (use get_curriculum_dataset). Returns exactly one record, or an error if the id is unknown. Requires no authentication.

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": {
      "id": "<id>"
    },
    "name": "get_classroom_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Output Schema

NameRequiredDescriptionDefault
idYesTool identifier, e.g. sight-words-first-grade
creatorYesTool creator, always Birkan Yavuz
objectiveYesLearning objective the tool teaches
gradeLevelYesGrade band the tool targets
invocation_idYesUnique receipt id for this call

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedOutput schema / properties / creator / description
      Added value: +"Tool creator, always Birkan Yavuz"
    • addedOutput schema / properties / gradeLevel / description
      Added value: +"Grade band the tool targets"
    • addedOutput schema / properties / id / description
      Added value: +"Tool identifier, e.g. sight-words-first-grade"
    • addedOutput schema / properties / invocation_id / description
      Added value: +"Unique receipt id for this call"
    • addedOutput schema / properties / objective / description
      Added value: +"Learning objective the tool teaches"
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior. The description adds useful behavioral context beyond annotations: exactly one record is returned, unknown ids produce an error, and no authentication is required.

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 focused sentences, front-loads the core action and identifier requirement, then covers usage and behavior. Every sentence adds useful information without repetition.

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 one required parameter, an output schema, and rich annotations, the description covers all agent-relevant decision points: when to use it, alternatives, return cardinality, error behavior, and authentication requirements.

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?

Schema coverage is 0%, so the description must explain the single id parameter. It specifies an exact identifier, gives an example, and notes typical sources from search/list results, though it does not detail the full id format beyond the example.

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: "Return one interactive classroom tool by its exact identifier," and includes an example. It clearly distinguishes this lookup tool from search/list/dataset siblings.

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 states when to use this tool (when already holding a tool id), where ids typically come from, and when not to use it, naming search_classroom_tools and get_curriculum_dataset as alternatives.

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.