Skip to main content
Glama

Modellix Media Generation

modellix_get_schema

Read-onlyIdempotent

Read the public executable input schema for an exact provider/model slug. No API key is forwarded to the schema host. Preserve required fields, defaults and references when preparing input.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "model_slug": "<model_slug>"
    },
    "name": "modellix_get_schema"
  }
}

Input Schema

NameRequiredDescriptionDefault
model_slugYesExact provider/model slug, with no default model.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavior: that the schema host is public and that "no API key is forwarded" to it, which is a meaningful disclosure about credential handling for an authenticated service. It does not cover failure behavior for an unknown slug, which keeps it from a 5.

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 with the purpose front-loaded, then the credential-handling caveat, then the practical instruction about preserving required fields. No hedging, no redundant restatement of the title, and each sentence contributes a distinct fact.

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 the description need not explain the returned schema document itself, and with one parameter there is little surface area to cover. The instruction to "preserve required fields, defaults and references" usefully signals that the returned schema is authoritative for downstream input construction. Only the behavior on a non-existent slug is left unspecified.

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% and there is a single required parameter, so the schema already documents model_slug as an exact provider/model slug with no default. The description restates "exact provider/model slug" without adding format examples, case sensitivity, or lookup failure semantics. Baseline 3 is appropriate when the schema carries the weight.

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?

"Read the public executable input schema for an exact provider/model slug" names a specific verb (read) and a specific resource (executable input schema keyed by model slug). That resource is distinct from what siblings like modellix_list_models or modellix_get_task would return, so an agent can mostly differentiate without opening the schema. It stops short of an explicit contrast sentence naming the closer alternatives, so it lands at 4 rather than 5.

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?

Usage is only implied: "when preparing input" hints that this is a pre-call step, but the description never says when to use this versus modellix_list_models or modellix_get_task, nor does it state any exclusion. An agent can infer the context but must reason about it rather than read it.

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.