Skip to main content
Glama

Bettyapp for Teachers

The curricula and courses with a study guide

list_curricula
Read-onlyIdempotent

Every board, exam body or curriculum with a study guide on Bettyapp (Ontario, OCR, Cambridge International, Singapore ...), each with its guides: the guide's id, title, course, Subject, Level, grade and how many topics it has. Useful for a guide's id, and for which courses Bettyapp follows. It lists only the guides Bettyapp shows. Example: the guide "ontario/physics/grade-12", "Studying Ontario Grade 12 Physics (SPH4U)".

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_curricula"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally. The description adds a genuine behavioral constraint in 'It lists only the guides Bettyapp shows', which tells the agent results are a curated subset, but it says nothing about result size, pagination or ordering.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The key scope statement is front-loaded and the compact field list is efficient. It is a single run-on sentence with a trailing example, which is slightly sprawling but every clause carries information.

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?

With no parameters and no output schema, the description carries the burden of explaining what comes back, and it does list the returned fields and the curated-subset behavior. For a zero-argument read tool this is close to complete, though ordering and result volume remain unstated.

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 takes no parameters and the schema is an empty object at 100% coverage, so there is nothing for the description to clarify. Baseline 4 applies.

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 names the resource precisely ('every board, exam body or curriculum with a study guide') and enumerates the returned fields (guide id, title, course, Subject, Level, grade, topic count), so an agent knows exactly what it gets. It does not, however, differentiate itself from siblings such as find_by_curriculum or get_levels.

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?

'Useful for a guide's id, and for which courses Bettyapp follows' implies the use cases, which is better than nothing. There is no explicit when-not guidance and no named alternative tools, so routing between this and find_by_curriculum is left to inference.

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.

Resources