Skip to main content
Glama
Sign In
Vitrine MCP Server

Vitrine MCP Server

Official
by vitrine3d
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get Config

vitrine_get_config

Retrieve the complete merged scene configuration for a model, combining look, layout, and overrides into a single output.

Instructions

Get the full merged scene config for a model (look + layout + overrides).

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_id": "<model_id>"
    },
    "name": "vitrine_get_config"
  }
}

Input Schema

NameRequiredDescriptionDefault
model_idYesModel ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.0
  2. Removedv1.0.0
  3. First observedv0.2.1

TDQS

A3.5/5.0
Behavior2/5

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

No annotations provided, and the description only states it retrieves data. It does not disclose whether authentication is required, rate limits, side effects, or return behavior. For a read operation, more detail is needed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, concise and front-loaded with the key action and result. No wasted words, but could include more detail without losing conciseness.

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 tool with one parameter and no output schema, the description is mostly adequate. It specifies the scope (merged scene config) and components (look, layout, overrides). Some examples or output hints would improve completeness.

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 100% for the single parameter (model_id). The description adds no additional semantic meaning beyond the schema's string type, so baseline 3 is appropriate.

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?

Description clearly states the tool gets the full merged scene config for a model, specifying it includes look, layout, and overrides. This clearly distinguishes it from siblings like vitrine_set_config (set config) and vitrine_model_info (model metadata).

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?

No explicit guidance on when to use this tool versus alternatives, nor any prerequisites or exclusions. The description implies it is for retrieving config, but lacks context for decision-making.

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