Skip to main content
Glama

List tested setups

list_tested_setups
Read-onlyIdempotent

Lists setup recipes, tested ones first. Each has the job, the first message to paste, the Ask first rules it needs, and honest notes on how the test went and what went wrong.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many to return. Default 8.
queryNoWords to match in the title or the job.
stackNoConnector ids the owner uses, such as gmail.
industryNoThe kind of business.
tested_onlyNoOnly setups that were really run. Default true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is fully covered. The description adds real value by naming the return payload (job, first message, Ask-first rules, test notes), though it says nothing about pagination/limit behavior beyond the schema or how filters combine.

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 the ordering constraint front-loaded and the return contents enumerated without preamble. Slightly padded by the colloquial "honest notes on how the test went and what went wrong," but every clause carries 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?

With no output schema, the description usefully tells the agent what each returned setup contains, which is the main unknown. Filters and defaults are fully covered by the schema, so the remaining gap is only guidance on choosing this tool over its siblings.

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 description coverage is 100%, so all five parameters are already documented in structured form; the baseline is 3. The description's only parameter-adjacent contribution is "tested ones first," which loosely reinforces the tested_only default but adds no new syntax or semantics.

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 ("Lists setup recipes") plus the ordering rule ("tested ones first"), so the agent knows it is a listing tool rather than a search. It does not explicitly distinguish itself from search_setups or get_setup, leaving the agent to infer the boundary from the names.

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 "tested ones first" implies this is the browse-the-library entry point, which is weak but usable usage context. There is no explicit statement of when to prefer this over search_setups or get_setup, and no mention of how the result set is narrowed.

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