Skip to main content
Glama

Civitai

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Search Models

search_models
Read-onlyIdempotent

Search Civitai's catalog of community AI image-generation models (Stable Diffusion checkpoints, LoRAs, textual-inversion embeddings, ControlNets) by text query and/or type. Returns download stats, base model (SDXL / Pony / Flux / SD 1.5), creator and trained trigger words. Defaults to Safe-For-Work (mature content excluded). Keyless.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoSort order: "Highest Rated", "Most Downloaded", or "Newest". Default "Most Downloaded".
typeNoModel type filter. One of: Checkpoint, LORA, TextualInversion, LoCon, Controlnet.
limitNoNumber of results, 1-25. Default 10.
queryNoText search over model names/descriptions, e.g. "realistic", "anime", "pixel art".
include_matureNoInclude mature/NSFW models. Default false (Safe-For-Work — sends nsfw=false to the API).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "limit": 10,
+    "query": "realistic portrait",
+    "sort": "Most Downloaded",
+    "type": "Checkpoint"
+  },
+  {
+    "include_mature": false,
+    "limit": 5,
+    "query": "anime",
+    "type": "LORA"
+  }
+]
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint. Description adds 'Keyless' (no auth needed) and 'Defaults to Safe-For-Work', which are behavioral traits not covered by annotations. No contradictions.

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 concise sentences that front-load the core purpose. No redundant wording; every phrase serves a purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Even without an output schema, the description lists return fields (download stats, base model, creator, trigger words) and covers model types, search modes, and maturity filtering. Fully adequate for a search tool.

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 baseline 3. Description reinforces 'Keyless' and provides usage examples that clarify parameter usage, adding value beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses specific verbs and nouns: 'Search Civitai's catalog of community AI image-generation models' and lists model types. It clearly distinguishes from siblings like 'get_model' (single retrieval) and 'list_by_type' (no search).

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 states default Safe-For-Work and that it's keyless, implying open usage. However, it does not explicitly contrast with siblings like 'get_model' or 'list_by_type', so the guidance is slightly implicit.

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

All Civitai toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources