Skip to main content
Glama
vitrine3d

Vitrine MCP Server

Official

Get Config

vitrine_get_config

Retrieve the complete merged scene configuration for a model, including look, layout, and override settings.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
model_idYesModel ID

Implementation Reference

  • The 'vitrine_get_config' tool is registered via server.registerTool inside registerConfigTools().
    export function registerConfigTools(server: McpServer, client: VitrineClient) {
      server.registerTool(
        "vitrine_get_config",
        {
          title: "Get Config",
          description: "Get the full merged scene config for a model (look + layout + overrides).",
          inputSchema: z.object({
            model_id: z.string().describe("Model ID"),
          }),
        },
        async ({ model_id }) => {
          const res = await client.getConfig(model_id);
          if (!res.ok) return { content: [{ type: "text", text: `Error: ${res.data?.message ?? res.status}` }], isError: true };
          return { content: [{ type: "text", text: JSON.stringify(res.data, null, 2) }] };
        },
      );
  • The handler function: receives model_id, calls client.getConfig(model_id), and returns the full merged scene config as JSON text.
    async ({ model_id }) => {
      const res = await client.getConfig(model_id);
      if (!res.ok) return { content: [{ type: "text", text: `Error: ${res.data?.message ?? res.status}` }], isError: true };
      return { content: [{ type: "text", text: JSON.stringify(res.data, null, 2) }] };
    },
  • Input schema: requires a 'model_id' (string). Title: 'Get Config'. Description explains it gets the full merged scene config (look + layout + overrides).
    {
      title: "Get Config",
      description: "Get the full merged scene config for a model (look + layout + overrides).",
      inputSchema: z.object({
        model_id: z.string().describe("Model ID"),
      }),
    },
  • The VitrineClient.getConfig() method makes a GET request to /v1/models/{modelId}/config — the underlying HTTP call powering the tool.
    getConfig(modelId: string) {
      return this.request("GET", `/v1/models/${modelId}/config`);
    }
Behavior3/5

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

With no annotations, the description carries the full burden. It states it retrieves a merged config, indicating a read operation. However, it does not disclose any potential behavioral traits such as performance implications or data freshness (e.g., cached vs real-time).

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?

The description is a single, front-loaded sentence of 13 words. Every word contributes meaning, with no redundancy or fluff.

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

Completeness2/5

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

No output schema is provided, and the description does not explain what the returned 'full merged scene config' looks like or its structure. Given the complexity of the return value, this is a notable gap.

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% with a single parameter 'model_id' described as 'Model ID'. The description adds no additional semantics beyond the schema, such as format or source of model IDs. Baseline 3 is appropriate given high schema coverage.

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 clearly states 'Get the full merged scene config for a model', specifying the verb 'get' and the resource 'full merged scene config'. It also clarifies that the config is composed of 'look + layout + overrides', distinguishing this tool from siblings like vitrine_set_config which writes config.

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?

The description implies usage for retrieving config, but does not explicitly state when to use this tool versus alternatives like vitrine_set_config or vitrine_apply_look. No exclusions or prerequisites are mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/vitrine3d/mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server