Skip to main content
Glama

Shortlist SaaS

Search listings

search_listings
Read-only

The live listings in the categories, plus the listings whose text contains the words of the need. Each listing has the TypeSafe score when one is already cached for this need, and it scores no listing. Without categories, the tool finds the category of the need first (one AI call). When the need fits more than one category, it returns choices: call again with one or two of them. Pass the returned categories to shortlist, so that it does not find the category again.

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": {
      "need": "<need>"
    },
    "name": "search_listings"
  }
}

Input Schema

NameRequiredDescriptionDefault
needYesWhat the person needs from a SaaS product, in plain words. For example: track the visits to my website.
categoriesNoOne or two category slugs from list_categories. Leave it out to let the tool find the category of the need.

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 readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds real behavioral context beyond that: the extra AI call when categories are omitted, that TypeSafe scores appear only when cached, that no scoring occurs here, and that ambiguous needs produce a `choices` response requiring a follow-up call. The only gap is that the exact shape of the `choices`/`categories` return values is not spelled out.

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

Conciseness3/5

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

The key scoping and chaining information is front-loaded, but the sentence 'Each listing has the TypeSafe score when one is already cached for this need, and it scores no listing' is convoluted and reads awkwardly. The description is serviceable but could be tightened considerably.

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 carries the burden of explaining returns, and it does describe the main return elements (listings, cached TypeSafe scores, `choices`, `categories`). It is nearly complete for a two-parameter read tool, though the precise structure of `choices` and the listing objects remains implicit.

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 coverage is 100%, so the baseline is 3, but the description adds meaning the schema lacks: omitting `categories` triggers an AI category-resolution call, and the returned `categories` should be reused downstream. That cost/flow context is genuinely useful beyond the schema's 'leave it out to let the tool find the category'.

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?

The description names the resource (live listings) and the retrieval logic (category listings plus text matches on the need), which is specific enough to separate it from get_listing and list_categories. The phrasing 'The live listings in the categories, plus the listings whose text contains the words of the need' is grammatically loose but conveys a clear verb+resource+scope.

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?

It gives concrete workflow guidance: omit categories to let the tool resolve the category (costing one AI call), and when the need spans multiple categories it returns `choices` and you should call again with one or two. It also tells the caller to pass the returned `categories` to shortlist to avoid re-resolution. It does not explicitly say when to prefer get_listing over this tool, but the chaining guidance is strong.

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