Skip to main content
Glama

Benchmark AP Classroom Curriculum & CED Search

list_live_bundles_and_checkouts

Returns live verified HTTP 200 checkout URLs for all 4 Native Teachers Pay Teachers Growing Bundles (#18343064 AP Psych Full-Year $12.19 35% OFF, #18343114 AP Precalc Full-Curriculum $13.81 35% OFF, #18336125 AP Psych Unit 3 $13.12 30% OFF, #18338841 AP Precalc Unit 3 $14.87 30% OFF), all 16 live V3 Dual-Format TpT classroom packs, live $12.99 Launch Special 40-question AP Udemy Practice Exam Simulators (couponCode=LAUNCH2026_APPSYCH for AP Psych Unit 3 and couponCode=LAUNCH2026_PRECALC for AP Precalc Unit 3, valid through Dec 15, 2026), Amazon KDP Print Workbooks (Live on Amazon ($16.99) InStock AP Psychology Unit 3 ASIN B0HRR3H727 / ISBN 9798142642141 at https://www.amazon.com/dp/B0HRR3H727, Live on Amazon ($16.99) InStock AP Precalculus Unit 3 ASIN B0HRQJLPRZ / ISBN 9798142561688 at https://www.amazon.com/dp/B0HRQJLPRZ, Live on Amazon ($24.99) InStock Corporate L&D ASIN B0HRQFWFPR / ISBN 9798142559005 at https://www.amazon.com/dp/B0HRQFWFPR, Publishing on Amazon ($24.99) Production LLM Evals ISBN 9798142670465, and AP Psychology Units 1 & 2 ($18.99, 116pp) releasing Nov 22), and instant Card / Apple Pay Whop vaults ($29 AP Cram + Canvas QTI 1.2 Vault at https://whop.com/checkout/plan_N08bOBkWmBFNE/, $79 Enterprise AI Eval & REA AgentEnv Pro Kit, $99 Corporate L&D SOP-to-SCORM Factory).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full behavioral burden. The claim of 'live verified HTTP 200' URLs is not a disclosure of tool behavior but a static data assertion; nothing is said about whether the returned list is a fixed snapshot or fetched at runtime, whether prices and discounts can be stale, whether the Amazon/Whop links are reachability-checked on each call, or how expired coupons (Dec 15, 2026) are handled. With zero annotation coverage this is a significant gap for a tool whose entire value proposition is freshness.

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

Conciseness1/5

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

A single ~250-word sentence that inlines four TpT bundle IDs with prices and discount percentages, sixteen classroom packs, two coupon codes, five Amazon ASINs/ISBNs and three Whop vault prices. Every one of those facts belongs in the returned payload, not in the tool description, and the lack of any sentence break makes it non-scannable for an agent.

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?

With no output schema, the description does have to convey what comes back, and it does so exhaustively — arguably too exhaustively — so an agent knows the shape of the response. But it omits the context that actually matters for correct invocation: freshness guarantees, whether the list is static, and how it relates to the sibling list/search tools.

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 disambiguate. Baseline 4 applies; no parameter meaning is added or needed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening clause names a specific verb and resource ('Returns live verified HTTP 200 checkout URLs'), which is a genuine statement of purpose, and the subject matter (paid bundles/checkouts) differs from the course/lesson/rubric siblings. However, the actual purpose is immediately buried under a catalog enumeration of product IDs, prices, ASINs and coupon codes, so an agent must parse a wall of commerce data to extract what the tool does.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no when-not-to-use, and no reference to the sibling tools that would help an agent decide between fetching purchasable checkout links versus searching lessons or rubrics. The description never states the condition that should trigger this call.

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.