Skip to main content
Glama

Benchmark AP Classroom Curriculum & CED Search

search_ap_lessons_and_rubrics

Searches Benchmark AP (@BenchmarkAP) classroom micro-lessons, CED topic tables, FRQ/SAQ/AAQ/EBQ scoring checklists, and printable guided-notes packets by keyword (e.g., 'concavity', 'rate of change', 'AAQ', 'EBQ', 'Phillips curve', 'demographic transition', 'SAQ', 'stimulus').

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": {
      "query": "<query>"
    },
    "name": "search_ap_lessons_and_rubrics"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesAP course name, CED topic number, exam skill, or concept keyword.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, yet it only says the tool searches. 'Searches' implies a non-destructive read, but nothing is said about result format, whether matches span all four content types at once, pagination, or any limits on result count.

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?

A single front-loaded sentence with the search scope stated before the examples; nothing is redundant. The content-type list is long but each item earns its place by narrowing scope, though the parenthetical examples could be trimmed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter, read-only search with no output schema and no annotations, the definition covers what is searchable but not what comes back or how to interpret it. Adequate to invoke, thin on what to expect.

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 100%, so the baseline would be 3, but the description adds concrete value by listing real query terms, including exam acronyms (AAQ, EBQ, SAQ) and stimulus-based queries that the schema's generic 'concept keyword' wording does not illustrate. That materially helps an agent construct a valid query.

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 opens with a specific verb ('Searches') and enumerates the concrete resource set it covers: classroom micro-lessons, CED topic tables, FRQ/SAQ/AAQ/EBQ scoring checklists, and guided-notes packets. That scope implicitly separates it from sibling get_ap_rubric_guide, but no sibling is named explicitly.

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?

Usage is only implied through the enumerated content types and keyword examples ('concavity', 'Phillips curve', 'stimulus'). There is no statement of when to prefer this over get_ap_rubric_guide or list_ap_courses_and_playlists, and no exclusions or prerequisites.

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.