Skip to main content
Glama
Sign In

authority.md

by md.authority
OverviewDiscussionsAdmin

search_personas

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.

Input Schema

NameRequiredDescriptionDefault
typeNoOptional filter to only personas, only skills (Tools), only playbooks, or only bundles.
limitNo
queryYesFree-text search across name, focus, tagline, and category.
categoryNoOptional category filter (e.g. 'Investor', 'Strategy').

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / type / description
      Previous 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."
    • changedInput schema / properties / type / enum
      Previous value: -[
-  "persona",
-  "skill",
-  "bundle"
-]New value: +[
+  "persona",
+  "skill",
+  "playbook",
+  "bundle"
+]
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It usefully discloses the result shape ('type', slug, focus, price) and warns that current prices live at an external URL, which is real added context. However it says nothing about permissions, result limits/pagination behavior, or rate limits for a read tool that defaults to 10 and caps at 50.

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

Conciseness4/5

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

Purpose and scope are front-loaded in the first clause, and every sentence adds usable detail (product types, pricing, trigger conditions, result fields). It is dense and somewhat long, but not padded.

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?

With no output schema, the description compensates by naming the returned fields ('type', slug, focus, price) and the pricing caveat. Given the sibling tools, it stops short of telling the agent when to escalate to get_persona_details or purchase_persona, which is the main remaining gap.

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?

Schema description coverage is 75% and the four product types are enumerated in the description, which enriches the meaning of the 'type' enum values well beyond the schema's terse gloss. The query, category, and limit parameters get no additional explanation, but the schema already documents them.

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+resource ('Search the authority.md marketplace') and describes the four product types it covers, which lets an agent distinguish broad search from a details lookup. It does not explicitly name its siblings (get_persona_details, list_categories), so differentiation is inferred rather than stated.

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

Usage Guidelines4/5

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

Gives clear trigger conditions: 'Use when the user asks about a specific person, a category, a task they want help with, or wants recommendations.' This is solid context, but it names no alternatives or when-not-to-use cases (e.g. when to prefer get_persona_details or list_categories).

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

All authority.md toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources