Skip to main content
Glama

Modellix Media Generation

modellix_list_models

Read-onlyIdempotent

Discover available media models with filters and pagination. Choose a precise slug before reading its schema. Prices, when present, are indicative.

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

Input Schema

NameRequiredDescriptionDefault
typeNoExact model type filter.
limitNo
offsetNo
keywordNoSearch slug and description.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered without the description's help. The description does add two pieces of genuine behavioral context — that results are paginated and that price values are indicative rather than authoritative — but it says nothing about result ordering or how paging terminates.

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?

Three short sentences, front-loaded with the action and scope, then the workflow hint, then the data caveat. Nothing is redundant with the title or the annotations, and each sentence carries distinct 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?

An output schema exists, so return-value detail is rightly omitted, and the description covers the essential contract for a filtered, paginated listing tool. The remaining shortfall is the undocumented limit/offset semantics, which matters for an agent paging through a large model catalog.

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 50%: type and keyword are documented in the schema, while limit and offset carry only defaults and bounds. The phrase "filters and pagination" maps loosely onto those four parameters but adds no format, matching semantics, or guidance on choosing a sensible limit, so the description neither compensates for the gap nor repeats the schema.

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?

"Discover available media models with filters and pagination" gives a specific verb and resource, and the follow-on clause ("before reading its schema") implicitly distinguishes this listing tool from the schema-reading sibling. It stops short of naming that sibling explicitly, so an agent must infer the routing rather than read it.

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?

The description establishes a clear workflow: use this tool to pick a precise slug, then go read that model's schema. It gives no explicit when-not guidance (e.g., what to do if you already know the slug, or whether to filter by type vs keyword), so usage is clear in context but not exhaustively bounded.

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.