Skip to main content
Glama

Find Tested setups

find_tested_setups
Read-onlyIdempotent

Only setups that were run for real (label "tested"), best matches first, each with its page link and a note on how it was tested. Leave the query empty to list them.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many to return (default 5).
queryNoOptional: the job, problem or tool, in plain words.
platformNoOptional platform id, such as claude, claude-code, chatgpt, gemini or grok-bot.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world and non-destructive behavior, so the safety profile is covered. The description adds value beyond that by disclosing the result ordering (relevance-ranked) and the shape of each item (page link plus how-it-was-tested note), which annotations cannot express.

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?

Two short sentences with no filler; the filtering condition and ranking lead, and the empty-query hint closes. The phrasing "run for real" is slightly informal but still compact and clear.

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 three optional parameters, no output schema, and safety already covered by annotations, the description supplies the remaining essentials: what qualifies for inclusion, how results are ordered, and what each result contains. Only the cross-tool routing versus sibling search/list tools is missing.

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 100%, so all three parameters are already documented, making 3 the baseline. The description adds one real semantic detail not in the schema: an empty query is a valid list-all mode, and query results are ordered by match quality. It says nothing further about limit or platform beyond what the schema provides.

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 with scope: it returns only setups labeled "tested", ranked best-match-first, each with a page link and a testing note. That implicitly distinguishes it from a general setup search, but it never names search_setups or list_tested_setups, so sibling differentiation is left to inference.

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 phrase "Leave the query empty to list them" gives one concrete usage mode, which is genuinely helpful. However, there is no guidance on when to prefer this over search_setups or list_tested_setups, and no exclusions or prerequisites are stated.

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