Skip to main content
Glama

Discover the Tools

search_tools

Read-onlyIdempotent

Search published, reviewed catalogue entries by task or name. Cite listing URLs. Not exhaustive; no held drafts, AI generation or paid ranking.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_tools"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
pricingNo
categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, and the description adds real context: the index covers only published, reviewed entries, excludes held drafts and AI-generated or paid-ranked results. It stops short of describing ranking order beyond that or how limit truncation behaves.

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?

Three short sentences, each earning its place, with the core purpose and the cataloguing scope front-loaded before the citation instruction.

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

Completeness3/5

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

With no output schema, "Cite listing URLs" usefully hints results contain listing URLs, and the coverage caveat sets expectations. Gaps remain around the filter parameters and result count behavior, which matter for a 4-parameter search tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry parameter meaning, and it only clarifies that query matches task or name. The pricing enum, category slug, and limit parameters are given no semantic explanation in either place.

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?

Specific verb plus resource: "Search published, reviewed catalogue entries by task or name" tells the agent exactly what is searched and over which fields. It implicitly separates itself from retrieval/listing siblings by emphasizing a query-driven search over a reviewed subset, though it does not name an alternative.

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

Usage Guidelines3/5

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

"Not exhaustive; no held drafts, AI generation or paid ranking" gives a useful when-results-will-be-missing exclusion, and "Cite listing URLs" implies a citation workflow. However, there is no positive guidance on when to prefer this over get_tool, list_categories, or compare_tools.

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