Skip to main content
Glama

Benchmark AP Classroom Curriculum & CED Search

list_ap_courses_and_playlists

Lists all Benchmark AP (@BenchmarkAP) high school Advanced Placement courses (AP Precalculus, AP Psychology New 5-Unit CED, AP Macroeconomics, AP Human Geography, AP World History: Modern), official YouTube course playlists, CED unit coverage, and printable 300-DPI Teachers Pay Teachers packet links.

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

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?

With no annotations, the description carries the full load, and "Lists" plus the enumerated output categories reasonably signal a read-only catalog. It does disclose the content of the response (courses, playlists, CED unit coverage, packet links), which matters since there is no output schema. It says nothing about result size, whether the catalog is static, or any auth/rate constraints, so real behavioral gaps remain.

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?

One front-loaded sentence with the verb first and the return categories after it; no filler or repetition. The long parenthetical course enumeration is dense but genuinely informative rather than wasteful.

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?

For a zero-parameter, read-only catalog tool with no annotations and no output schema, the description supplies the key missing piece: what the response contains. An agent can call it correctly with no further information. Only minor context, such as whether the listing is exhaustive or scoped to Benchmark AP content, is 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 zero parameters, so the schema baseline applies and there is nothing for the description to disambiguate. The description correctly implies no inputs are needed to retrieve the full catalog.

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?

"Lists all Benchmark AP ... high school Advanced Placement courses ... official YouTube course playlists, CED unit coverage, and ... packet links" gives a specific verb plus a concretely enumerated resource set, so an agent knows exactly what comes back. It does not explicitly name a sibling or state how it differs from search_ap_lessons_and_rubrics, but the catalog-vs-search distinction is readable from the wording.

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?

There is no explicit when-to-use statement, no exclusions, and no named alternative. Usage is only implied: an agent infers this is the discovery/catalog entry point before drilling into lessons or rubrics via the sibling tools. Adequate for a zero-parameter listing tool, but the routing guidance 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.