Skip to main content
Glama

Search listings

agentwares_search

Search the catalog of workflows, prompt packs, MCP configs, playbooks, datasets and tools. No key needed.

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

Input Schema

NameRequiredDescriptionDefault
qNoKeywords matched against title, summary, tags and description.
sortNo
limitNo
offsetNo
api_keyNoYour Agentwares API key. Optional when the MCP connection already sends an Authorization: Bearer header.
categoryNo
max_priceNoMaximum price in credits.
pricing_modelNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses that no API key is required, but says nothing about pagination behavior, result ordering, rate limits, or what a result set contains.

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?

Two short sentences, front-loaded with the resource and scope, with zero filler. Nothing is wasted or buried.

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

Completeness2/5

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

For an 8-parameter search tool with no annotations and no output schema, the description is too thin. It omits how results are returned, how filters combine, and how to page through results, leaving the agent to guess at core behavior.

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 coverage is only 38% across 8 parameters, so the description should compensate but does not. The "No key needed" line loosely relates to the optional api_key parameter, but q, sort, limit, offset, max_price, and pricing_model get no added meaning beyond the schema.

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 ("the catalog") and enumerates the content types covered (workflows, prompt packs, MCP configs, playbooks, datasets, tools). It does not distinguish itself from siblings like agentwares_get_listing or agentwares_library, so an agent must infer the boundary.

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

Usage Guidelines2/5

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

The only usage guidance is "No key needed," which is an auth note rather than a when-to-use rule. Nothing says when to search versus fetching a specific listing via agentwares_get_listing, or how to narrow with category/pricing filters.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources