Skip to main content
Glama
Cloady

Cloady

Official
by Cloady

List Templates

listTemplates
Read-only

Search, filter, sort, and paginate the Cloady template catalog without a token; total and per-category counts reflect all applied filters.

Instructions

Search, filter, sort and page the template catalog. Public: no token needed. total counts every match, and categories counts the matches in each category with every other filter applied. Omit limit for every match.

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

Input Schema

NameRequiredDescriptionDefault
qNo
sortNopopular
limitNo
priceNo
offsetNo
categoryNo
maxPriceNo
minRatingNo
withDatabaseNo
singleServiceNo
updatedThisWeekNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changedv0.18.0
    • addedInput schema / properties / category
      Added value: +{
      +  "maxLength": 60,
      +  "type": "string"
      +}
    • addedInput schema / properties / limit
      Added value: +{
      +  "maximum": 500,
      +  "minimum": 1,
      +  "type": "number"
      +}
    • addedInput schema / properties / maxPrice
      Added value: +{
      +  "maximum": 9007199254740991,
      +  "minimum": 0,
      +  "type": "number"
      +}
    • addedInput schema / properties / minRating
      Added value: +{
      +  "maximum": 5,
      +  "minimum": 0,
      +  "type": "number"
      +}
    • addedInput schema / properties / offset
      Added value: +{
      +  "default": 0,
      +  "maximum": 9007199254740991,
      +  "minimum": 0,
      +  "type": "number"
      +}
    • addedInput schema / properties / price
      Added value: +{
      +  "enum": [
      +    "free",
      +    "paid"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / q
      Added value: +{
      +  "maxLength": 100,
      +  "type": "string"
      +}
    • addedInput schema / properties / singleService
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / sort
      Added value: +{
      +  "default": "popular",
      +  "enum": [
      +    "popular",
      +    "rating",
      +    "updated",
      +    "price",
      +    "name"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / updatedThisWeek
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / withDatabase
      Added value: +{
      +  "type": "boolean"
      +}
  2. First observedv0.5.1

TDQS

A3.5/5.0
Behavior4/5

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

Beyond the annotations, which already declare a read-only, non-destructive, open-world operation, the description adds useful behavior: no token is needed, `total` reflects all matches, `categories` is computed with other filters still applied, and omitting `limit` returns everything. It does not cover rate limits or the shape of individual template items.

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?

The description is short, front-loaded with the core action, and has no filler. Each sentence adds either purpose, authentication, aggregate-return semantics, or pagination behavior.

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?

It covers purpose, public access, pagination, and some aggregate return semantics, which is helpful for an 11-parameter search tool. But with no output schema and no parameter descriptions, it leaves substantial gaps around individual filters, sorting behavior, and returned template data.

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% across 11 parameters, and the description explains only `limit` omission plus broad categories of filtering. It does not clarify the meaning or interactions of `q`, `category`, `price`, `maxPrice`, `minRating`, `sort`, `offset`, or the boolean filters beyond what their names imply.

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 clearly states a specific verb set (search, filter, sort, page) and resource (template catalog), so the agent knows this is a template-listing search endpoint. It does not explicitly distinguish itself from sibling tools, though no sibling appears to be a competing template-list operation.

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?

It gives concrete operational guidance for authentication and pagination: the catalog is public and omitting `limit` returns every match. However, it does not explicitly say when to use this versus template-related siblings such as `reviewTemplate` or `deleteTemplateReview`, so the when-to-use guidance is only implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools