Skip to main content
Glama

Get model schema

get_model
Read-onlyIdempotent

Return the published input schema for a supported model in Rainbrand’s public API. Follow its field names, limits, and accepted reference formats when constructing generation 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": "<model>"
    },
    "name": "get_model"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelYesModel to inspect. Copy its ID from a list_models result.
llm_modelNoThe model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Omit it or pass "unknown" if you are not certain; the tool runs the same either way. Recorded only for the server developer's analytics.

Output Schema

NameRequiredDescriptionDefault
idYesModel ID. Pass it as model to get_model and the generate tools.
nameYesDisplay name of the model.
typeYesType of file the model generates.
providerYesCompany that made the model.
descriptionYesShort description of the model.
capabilitiesYesMachine-readable tags identifying the model’s supported operations, such as `text-to-image` or `image-to-video`.
input_schemaYesPublished JSON Schema for generation input. Where a reference field accepts HTTPS URLs, Rainbrand handles any conversion required by the provider.

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?

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so safety behavior is largely covered. The description adds that the schema is 'published' and should be treated as authoritative for field names and limits, but says nothing about caching, freshness, auth, or failure modes for an unsupported model ID.

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 sentences, zero filler, with the core action stated first and the operative follow-up ('follow its field names, limits, and reference formats') second. Every clause earns its place.

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?

With an output schema present, the description needn't explain return values, and annotations cover the read-only profile; for a simple 2-parameter getter this is nearly complete. It could go further by explicitly pointing to list_models for obtaining valid IDs and by stating what happens for an unsupported model.

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 both parameters (model and the analytics-only llm_model) are fully self-documented, including the instruction to copy the ID from a list_models result. The description adds no parameter meaning beyond the schema, which is the expected baseline of 3 when the schema does the heavy lifting.

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?

States a specific verb and resource: 'Return the published input schema for a supported model.' This is clearly distinguishable from sibling getters like get_brand or get_account, which fetch entity data rather than schemas. It stops short of naming a specific sibling (e.g., list_models, referenced only in the parameter schema) so the agent must infer model IDs come from elsewhere.

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?

'Follow its field names, limits, and accepted reference formats when constructing generation input' gives clear context: call this before building generation payloads. There are no explicit exclusions or when-not conditions, and the dependency on list_models is only implied via the input schema, not the description.

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.

Resources