Skip to main content
Glama

Search marketplace blueprints

search_blueprints
Read-onlyIdempotent

Search public AI agent instruction blueprints—AGENTS.md, CLAUDE.md, Cursor rules, and slash commands—by query, type, category, or tags to find published templates; use get_blueprint to read one.

Instructions

Search the public LynxPrompt marketplace of AI agent instruction files (AGENTS.md, CLAUDE.md, Cursor rules, slash commands and so on). Use it to find blueprints other people published; get_blueprint reads a result's content. To find your own blueprints use list_blueprints instead. Needs no token. Returns one page of results (templates[] with id, name, description, author, type, tags) plus total and hasMore.

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": "search_blueprints"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, starting at 1. Default 1.
sortNoResult order. Default popular.
tagsNoMatch blueprints carrying any of these tags, e.g. ["react", "typescript"].
typeNo"configs" for instruction files, "commands" for slash commands and workflows. Leave out for both.
limitNoResults per page, 1 to 50. Default 12.
queryNoWords to match in name, description or tags, e.g. "nextjs". Leave out to list the most popular blueprints.
categoryNoCategory slug, e.g. web, devops, saas, mobile, data or other.

Output Schema

NameRequiredDescriptionDefault
totalNo
hasMoreNoTrue when another page exists: call again with page + 1
templatesNo
popularTagsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed16 schema fields changedv0.3.0
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / category / description
      Previous value: -"Filter by category (optional)"New value: +"Category slug, e.g. web, devops, saas, mobile, data or other."
    • addedInput schema / properties / category / maxLength
      Added value: +50
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "Results per page, 1 to 50. Default 12.",
      +  "maximum": 50,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / page
      Added value: +{
      +  "description": "Page number, starting at 1. Default 1.",
      +  "maximum": 1000,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • changedInput schema / properties / query / description
      Previous value: -"Search query string"New value: +"Words to match in name, description or tags, e.g. \"nextjs\". Leave out to list the most popular blueprints."
    • addedInput schema / properties / query / maxLength
      Added value: +200
    • addedInput schema / properties / sort
      Added value: +{
      +  "description": "Result order. Default popular.",
      +  "enum": [
      +    "popular",
      +    "recent",
      +    "downloads",
      +    "favorites"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / tags / description
      Previous value: -"Comma-separated tags to filter by (optional)"New value: +"Match blueprints carrying any of these tags, e.g. [\"react\", \"typescript\"]."
    • addedInput schema / properties / tags / items
      Added value: +{
      +  "maxLength": 30,
      +  "type": "string"
      +}
    • addedInput schema / properties / tags / maxItems
      Added value: +10
    • changedInput schema / properties / tags / type
      Previous value: -"string"New value: +"array"
    • changedInput schema / properties / type / description
      Previous value: -"Filter by type, e.g. AGENTS_MD, CLAUDE_MD (optional)"New value: +"\"configs\" for instruction files, \"commands\" for slash commands and workflows. Leave out for both."
    • addedInput schema / properties / type / enum
      Added value: +[
      +  "configs",
      +  "commands"
      +]
    • changedInput schema / required
      Previous value: -[
      -  "query"
      -]New value: +[]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "hasMore": {
      +      "description": "True when another page exists: call again with page + 1",
      +      "type": "boolean"
      +    },
      +    "popularTags": {
      +      "type": "array"
      +    },
      +    "templates": {
      +      "items": {
      +        "properties": {
      +          "author": {
      +            "type": "string"
      +          },
      +          "category": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "description": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "downloads": {
      +            "type": "number"
      +          },
      +          "id": {
      +            "type": "string"
      +          },
      +          "likes": {
      +            "type": "number"
      +          },
      +          "name": {
      +            "type": "string"
      +          },
      +          "tags": {
      +            "items": {
      +              "type": "string"
      +            },
      +            "type": "array"
      +          },
      +          "tier": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "type": {
      +            "type": "string"
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "total": {
      +      "type": "integer"
      +    }
      +  },
      +  "type": "object"
      +}
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds meaningful context beyond that: no authentication token is required, and results are paginated with total/hasMore. It does not mention rate limits or result-count ceilings, but the essential behavioral picture is present.

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?

Four short sentences, front-loaded with the core action and followed by routing guidance before any return-value detail. The final sentence describing the return shape partly duplicates the output schema, which is minor redundancy but does not obscure the key information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only, no-required-param search tool, the definition covers purpose, sibling routing, auth requirement, pagination semantics and result shape. With an output schema and full annotations backing it, an agent has everything needed to call this correctly on the first attempt.

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% and every parameter (page, limit, sort, query, tags, type, category) is documented inline with defaults and examples. The description adds no parameter-level guidance beyond that, so the baseline of 3 applies.

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

Purpose5/5

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

States a specific verb and resource ('Search the public LynxPrompt marketplace of AI agent instruction files') and enumerates the resource types covered. It explicitly distinguishes itself from both siblings—get_blueprint for reading content and list_blueprints for owned items—so an agent can route correctly without opening a schema.

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

Usage Guidelines5/5

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

Provides explicit when-to-use ('find blueprints other people published') and when-not-to-use with named alternatives ('To find your own blueprints use list_blueprints instead'), plus the follow-up step via get_blueprint. Nothing about tool selection is left to inference.

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