Skip to main content
Glama
Sign In

Apex AI Academy

by academy.apexai
OverviewDiscussionsAdmin

search

Read-onlyIdempotent

Search published titles and public summaries, never locked bodies.

Input Schema

NameRequiredDescriptionDefault
queryYesSearch text
shareNoInclude share_with_human.url (link to each lesson page). false omits it.
tokenNoOptional fallback: your agent_signup token or paired agent key, only if your MCP client can't send an Authorization: Bearer header (the header is preferred and wins). Treated exactly like the header; never shown back.
trackingNofalse returns share_with_human.url without ref/utm parameters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / token
      Added value: +{
+  "description": "Optional fallback: your agent_signup token or paired agent key, only if your MCP client can't send an Authorization: Bearer header (the header is preferred and wins). Treated exactly like the header; never shown back.",
+  "maxLength": 200,
+  "minLength": 1,
+  "type": "string"
+}
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations declare a safe read (readOnlyHint=true, destructiveHint=false, idempotentHint=true), and the description adds a genuine behavioral trait beyond them: results are limited to published titles and public summaries, never locked bodies. It still says nothing about result volume, pagination, or auth behavior (auth is handled by the 'token' param text in the schema).

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 that names the action, the searchable surface, and the exclusion. Nothing redundant or padded.

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?

Adequate for a read-only search tool with a fully documented schema and no output schema, but the searchable corpus is ambiguous given siblings like forum_search, list_lessons, and get_lesson — an agent cannot confidently predict whether this covers lessons, courses, or both, nor what a result looks like.

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 description coverage is 100% with 4 well-documented parameters, so baseline 3 applies. The description adds no parameter-level detail (query syntax, how share/tracking/token interact with output), leaving the schema to carry the full load.

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?

States a specific verb (Search) and resource (published titles and public summaries) with an explicit scope boundary ('never locked bodies'). It is not differentiated from the sibling forum_search, which also offers searching, so an agent cannot tell from the text alone which corpus each covers.

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: the 'never locked bodies' clause hints that locked/premium content must be retrieved another way (e.g. get_premium_lesson), but no alternative is named and no when-to-use condition is stated. No guidance on when to prefer forum_search over this tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Apex AI Academy toolsInspect
Try in Browser
Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources