search_curriculumFull-text search across Promptafire lessons. Returns module, section, whether it is free or Pro, a short snippet when readable, and the web URL.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | What to look for |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare the tool read-only and non-destructive, so the description only needs to add behavioral value. It does so by listing the returned fields and noting that snippets appear only 'when readable,' which is useful nuance. It does not mention limits or empty-result behavior, but these are minor for a simple search tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is one efficient sentence that front-loads the core action and then lists the return fields without filler. Every clause earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
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 tool with no output schema, the description adequately covers both what to pass and what to expect back. Missing details like pagination, result limits, and no-match behavior would be nice but are not critical given the tool's simplicity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and the query parameter already has a clear description in the schema. The tool description reinforces that the query is full-text but adds no new format, syntax, or example details beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific action and resource: full-text search across Promptafire lessons. It distinguishes itself from list/read tools by emphasizing search, though it does not explicitly differentiate from the generic sibling tool 'search'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies the tool is for finding lessons by free-text query, but it gives no explicit guidance about when to use it instead of siblings like search, read_lesson, or list_modules. Usage context is inferred rather than stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools are distinct, but fetch overlaps with read_lesson and read_post since both can return lesson/post markdown, and search/search_curriculum have similar scopes. The descriptions help clarify some boundaries, such as search returning ids for fetch, but an agent could still be uncertain which retrieval tool to use.
Tool names mostly follow a verb_noun pattern like list_modules, read_lesson, and get_module. The main inconsistencies are the bare verbs fetch and search, plus the mixed use of get versus read for similar retrieval actions.
Eight tools is well-scoped for a content platform covering curriculum browsing, lesson reading, blog posts, and search. Each tool has a reasonable place in the workflow without excessive redundancy.
The tool surface covers the full content lifecycle: discovering tracks/modules, listing posts, searching lessons and posts, retrieving module metadata, and reading full lesson or post markdown. Access-level handling is included, so there are no obvious dead ends for the stated purpose.