Skip to main content
Glama

Model geometry for the 3D view

vedutum_model_geometry
Read-onlyIdempotent

Returns the plan geometry (walls, openings, rooms, furniture, roof and facade settings) that the VEDUTUM 3D view draws. Used by the view itself.

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

Input Schema

NameRequiredDescriptionDefault
languageNoLanguage of the answer: "de" (German) or "en" (English). Default "de".
project_idNoProject id, as vedutum_list_projects returns it

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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=false, so the safety profile is covered structurally. The description adds genuine context by naming what the payload contains and who consumes it, but it says nothing about response size, latency, or whether geometry can be stale relative to recent edits. With annotations doing the heavy lifting, this is adequate but not rich.

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?

Two short sentences with no filler, and the payload enumeration is front-loaded before the consumer note. Nothing is redundant or padded. It is efficient, though the second sentence is thin enough that it could have carried more routing detail at the same length.

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

Completeness3/5

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

For a two-parameter read-only geometry fetch with full schema coverage and no output schema, the description covers purpose and consumer, which is the minimum viable set. However, with no output schema present, an agent gets no sense of the return shape or size beyond the parenthetical list. A brief note on the payload's scale or its relationship to vedutum_view_model would complete it.

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 the schema already documents language (with its de/en enum and default) and project_id (as returned by vedutum_list_projects). The description mentions no parameters at all, so it adds no meaning beyond the schema. The baseline of 3 applies when the schema fully carries parameter semantics.

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?

The description uses a specific verb and resource ('Returns the plan geometry') and enumerates the payload in parentheses: walls, openings, rooms, furniture, roof and facade settings. That is far clearer than a tautology. It stops short of 5 because it never distinguishes this from close siblings such as vedutum_view_model or vedutum_read_floor_plan, so an agent cannot route between them from the text alone.

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?

'Used by the view itself' implies this is an internal dependency of the rendering pipeline rather than a general-purpose query, which is a weak when-to-use signal. There is no explicit guidance on when an agent should call it instead of vedutum_view_model, and no exclusions or prerequisites. Usage is only implied, not stated.

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