Skip to main content
Glama

search_listings

Read-onlyIdempotent

Keyword search over the directory catalog (names, descriptions, tags, criteria marks). Returns matching listings with scores and what matched. This is keyword matching, not semantic search.

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_listings"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesQuestion-shaped or keyword query, e.g. "self-hosted tool with approval gates".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: the matching mechanism (keyword, not semantic) and the return shape (matching listings with scores and what matched). It omits result caps, pagination and ranking order, which keeps it from a 5.

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, all front-loaded: what it searches, what it returns, and the key caveat about matching mode. Nothing is redundant with the schema and no sentence could be cut without losing information.

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?

For a one-parameter read tool with no output schema, the description supplies the searched fields and a summary of the return value, which is what an agent needs to call it. The remaining gap is result volume behavior (limits or pagination) for broad keyword queries.

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?

With a single parameter at 100% schema coverage the baseline is 3, and the description earns above baseline by clarifying that the query is matched literally against names, descriptions, tags and criteria marks, so an agent knows free-text phrasing is acceptable rather than needing exact field syntax.

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 and resource (keyword search over the directory catalog) and enumerates the searched fields (names, descriptions, tags, criteria marks). The explicit 'keyword matching, not semantic search' clause pins down the retrieval mode, though it never names a sibling such as get_listing as the direct-lookup 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?

The 'not semantic search' note implies when this tool fits (literal keyword queries) versus a fuzzy/semantic approach, but there is no explicit when-to-use-vs-alternative routing, e.g. 'use get_listing when you already have an ID.' Usage is only implied.

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