Skip to main content
Glama

Benchmark AP Classroom Curriculum & CED Search

get_ap_rubric_guide

Returns the structured Free-Response scoring checklist, common exam traps, syllabus pacing topics, YouTube playlist URL, and printable TpT packet link for a specific AP course slug (e.g. 'ap-precalc', 'ap-psych-ced', 'ap-macro', 'ap-hug', 'ap-world') or guide slug.

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": {
      "identifier": "<identifier>"
    },
    "name": "get_ap_rubric_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
identifierYesCourse slug (e.g. 'ap-precalc', 'ap-psych-ced', 'ap-macro', 'ap-hug', 'ap-world') or lesson/guide slug.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the specific payload sections a caller will receive, so the agent knows what data to expect without an output schema. It omits what happens for an unrecognized slug and whether the returned links are external/printable-only, which keeps it from a 5.

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?

A single front-loaded sentence lists the returned artifacts immediately followed by the accepted identifier forms. Nothing is redundant or buried, and the payload summary comes before the parameter detail where an agent needs it.

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 one-parameter lookup with no annotations or output schema, the description is rich enough to predict the response. The remaining gap is failure behavior for an invalid or ambiguous slug and no explicit routing to sibling tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the schema already supplies slug examples with a description. The description repeats the same examples ('ap-precalc', 'ap-psych-ced') and adds only that a lesson/guide slug is also accepted, so it adds marginal meaning beyond the schema.

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 ('Returns') and enumerates the exact resource bundle (scoring checklist, exam traps, pacing topics, playlist URL, packet link) tied to one identifier. It is clearly a slug-keyed lookup tool, distinct in shape from the sibling list/search tools, though it never names an alternative.

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: 'for a specific AP course slug' suggests use when you already know the slug. There is no explicit when-to-use or when-not statement, and it does not tell the agent to fall back to search_ap_lessons_and_rubrics or list_ap_courses_and_playlists when the slug is unknown.

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.