Skip to main content
Glama

Legends of Learning

by com.legendsoflearning.app

Get a Legends of Learning game

legends_get_game
Read-only

Fetches the full public detail for one Legends of Learning game by its numeric id (from legends_search_games).

Returns the game's id, title, description, image, estimated_duration in minutes, type, grades served, teacher/student ratings, instructions, vocabulary, discussion questions, capability flags (supports_ipad, supports_tts, multi_language, saves_progress), lexile_level, the public url, and learning_objectives — the standards the game is aligned to, each with id, title, code, and standard_set.

Example: {"game_id": 1445} returns that game, or an error result if no such game is publicly available.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
game_idYesNumeric game id, e.g. from legends_search_games results

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true. The description adds behavioral context: it returns full public detail, specifies error handling (if no game is publicly available), and provides an example. No contradiction.

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 concise sentences: purpose, full return fields list, and example. No wasted words. Front-loaded with purpose.

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?

No output schema exists, so the description compensates by listing all expected fields. Includes error case and relation to sibling tool. Complete for a lookup tool.

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 parameter is well-described in schema (100% coverage). The description reinforces the source of the id and provides an example JSON, adding value 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 clearly states it fetches full public detail for a game by numeric id, distinguishing it from sibling tools. It specifically mentions the id source (legends_search_games) and lists all returned fields.

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

Usage Guidelines4/5

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

It provides context that the game_id comes from legends_search_games, implying prior use of that tool. It does not explicitly state when not to use, but the linking is clear enough for typical usage.

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

All Legends of Learning toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.6/5.0
Disambiguation5/5

Each tool has a distinct purpose: browsing standards, searching games, and fetching game details. No overlap or ambiguity in their functionality.

Naming Consistency5/5

All tools follow the 'legends_' prefix with a consistent 'verb_noun' naming pattern (browse_standards, get_game, search_games), making it predictable.

Tool Count4/5

With only 3 tools, the set is minimal but sufficient for the server's purpose of accessing the public Legends of Learning catalog. It could benefit from a few more, but it's reasonable.

Completeness5/5

The tools cover the core workflows: exploring standards, searching for games, and retrieving detailed game info. No obvious gaps for a read-only public API.

Resources