Search, browse, and buy AI thinking frameworks from within any MCP client. 597 frameworks drawn from the documented thinking of notable people, plus 24 functional Tools and 7 curated bundles, delivered as .md files and native Claude Skills.
Scored across 4 tools
Each tool has a clearly different primary action: searching, listing categories, viewing details, and purchasing. There is minor overlap because search_personas can also be used for category browsing, but the descriptions direct list_categories specifically to browsing by domain.
All tool names follow a consistent verb_noun pattern in lowercase snake_case: get, list, purchase, search. Minor plural differences (persona vs personas) do not obscure the pattern.
Four tools is well-scoped for a marketplace flow: discover by search, browse by category, inspect details, and complete purchase. Each tool has a clear place in the workflow with no redundancy.
The tool set covers the full marketplace journey from discovery to purchase, including bundle handling through get_persona_details returning required slugs for purchase_persona. No obvious dead ends remain for the stated purpose.
Get the full details for a specific product on authority.md — a persona framework, a functional Tool, a Playbook, or a curated Bundle. Use after search_personas to show complete information before purchase. Returns metadata, a 'type' field, and a preview of the content. Accepts persona slugs (e.g. 'warren-buffett'), Tool slugs (e.g. 'decision-brief'), Playbook slugs (e.g. 'invoice-chase'), and Bundle slugs (e.g. 'founder-stack'). For bundles, returns the full list of persona slugs needed to call purchase_persona.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | A persona slug (e.g. 'warren-buffett'), a skill slug (e.g. 'strategic-email'), a playbook slug (e.g. 'invoice-chase'), or a bundle slug (e.g. 'founder-stack'). |
List all categories of thinkers available on authority.md. Use when the user wants to browse by domain (Investor, Tech Visionary, Philosopher, etc.) rather than search by name.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden. It states this is a listing operation that returns all categories from authority.md, implying a safe read with no side effects. It does not describe the output shape or ordering, but for a simple category list this is a minor gap.
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?
Two tight sentences, with the core action front-loaded and the usage guidance immediately after. No filler or repeated schema content.
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 zero-parameter listing tool, the description gives enough context to choose and invoke it correctly. The only thing absent is an explicit statement of the return format (e.g., an array of category names), which is not critical for such a simple operation.
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?
There are no parameters, and the schema is an empty object with 100% coverage, so the baseline of 4 applies. There is nothing for the description to add.
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 uses a specific verb ('List') and resource ('all categories of thinkers available on authority.md'), with concrete examples (Investor, Tech Visionary, Philosopher). It clearly distinguishes the tool from name-based search, its main sibling.
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?
It gives an explicit use condition: when the user wants to browse by domain rather than search by name. Though it does not name search_personas directly, 'search by name' unambiguously identifies the alternative path.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Generate a checkout URL on authority.md for purchasing one or more frameworks, Tools, Playbooks, or Bundles. Accepts 1-50 slugs (personas, Tools, and/or Playbooks, mixed carts allowed). To purchase a Bundle, pass all 10 of its persona slugs (get them from get_persona_details on the bundle slug — they will land on the $29.99 step-pricing tier automatically). Returns a URL the user follows to a checkout page hosted by authority.md that processes payment securely via Stripe. Personas use step pricing; Tools have individual prices; Playbooks are a flat $12.99 each. For current prices call get_persona_details per slug or read https://authority.md/products.json. Confirm with the user which items they want and the total cost BEFORE calling this tool.
| Name | Required | Description | Default |
|---|---|---|---|
| slugs | Yes |
Search the authority.md marketplace. It carries four product types: persona thinking frameworks (e.g. Warren Buffett), hand-built functional Tools (e.g. Strategic Email — procedures for recurring tasks such as difficult emails, hiring, and pricing), Playbooks (systematically produced single-job procedures at a flat $12.99, e.g. Invoice Chase), and curated 10-persona Bundles (e.g. founder-stack, engineers-stack — $29.99 each). Use when the user asks about a specific person, a category, a task they want help with, or wants recommendations. Each result includes a 'type' field ('persona', 'skill', 'playbook', or 'bundle'), slug, focus, and price. For current prices read https://authority.md/products.json.
| Name | Required | Description | Default |
|---|---|---|---|
| type | No | Optional filter to only personas, only skills (Tools), only playbooks, or only bundles. | |
| limit | No | ||
| query | Yes | Free-text search across name, focus, tagline, and category. | |
| category | No | Optional category filter (e.g. 'Investor', 'Strategy'). |
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
get_persona_details1 field changedInput schema / properties / slug / descriptionPrevious value: -"A persona slug (e.g. 'warren-buffett'), a skill slug (e.g. 'strategic-email'), or a bundle slug (e.g. 'founder-stack')."New value: +"A persona slug (e.g. 'warren-buffett'), a skill slug (e.g. 'strategic-email'), a playbook slug (e.g. 'invoice-chase'), or a bundle slug (e.g. 'founder-stack')."search_personas2 fields changedInput schema / properties / type / descriptionPrevious value: -"Optional filter to only personas, only skills, or only bundles."New value: +"Optional filter to only personas, only skills (Tools), only playbooks, or only bundles."Input schema / properties / type / enumPrevious value: -[
- "persona",
- "skill",
- "bundle"
-]New value: +[
+ "persona",
+ "skill",
+ "playbook",
+ "bundle"
+]get_persona_detailslist_categoriespurchase_personasearch_personas
Add one secure layer between your agents and this server.