Skip to main content
Glama
crowllm-mcp

crowllm-mcp

Official
by crowwdev

Search CrowLLM models

search_models

Search the live CrowLLM model catalog by ID substring, set result limits, or return only zero-rated ':free' model IDs. Use it to find available models and free options for chat or pricing checks.

Instructions

Search the live CrowLLM catalog (GET /v1/models). Optionally return only zero-rated ':free' ids.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of ids (default 100)
queryNoSubstring to match against model ids
free_onlyNoOnly return ids ending in ':free'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It usefully discloses that the catalog is live and reached via GET (implying a read-only network call), but says nothing about rate limits, pagination, caching, or the shape of results beyond 'ids'.

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?

Two short sentences, front-loaded with the core action and resource, with no filler. Every clause contributes scope or option 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 simple read-only search with fully documented parameters and no output schema, the description covers action, source and the main option. Only the returned list shape and pagination/limit behavior are left implicit, which the schema largely covers.

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 limit, query and free_only are already documented. The description adds only the gloss 'zero-rated' for ':free' ids, which is a marginal semantic gain over the schema's 'Only return ids ending in :free'.

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?

Names a specific verb ('Search') and resource ('the live CrowLLM catalog') and even cites the underlying endpoint GET /v1/models, so the agent knows exactly what is being queried. It does not distinguish itself from siblings like chat or get_pricing, but their purposes are visually distinct.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use guidance, no mention of when to prefer get_pricing or chat instead, and no stated prerequisites. The only usage signal is implicit in 'live catalog', which suggests model discovery.

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