Skip to main content
Glama

Show a 3D model

vedutum_view_model
Read-onlyIdempotent

Shows a building model in 3D inside the conversation: turn it, look at single storeys or a cut-away view. Without project_id it shows VEDUTUM’s example house „Haus Lindenweg“ (no account needed); with project_id a project of the connected account. Returns a short summary for clients without the view.

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_view_model"
  }
}

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

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavior: the output is an interactive in-conversation 3D view, and clients without such a view receive a short textual summary instead — a fallback an agent could not infer from annotations. It does not state error behavior for an invalid or inaccessible project_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, no filler. The core action comes first, interaction modes follow, and the parameter/fallback behavior is packed into a compact second sentence.

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 only two optional parameters and no output schema, the description covers what the tool produces (a 3D view or a text summary) and both parameter regimes. Only edge cases such as invalid project_id or permissions failures remain unaddressed, which is minor for a read-only viewer.

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%, so both parameters are already documented, establishing a baseline of 3. The description does add meaning for project_id by explaining the presence/absence semantics (example house vs. account project) and notes account requirements, but says nothing beyond the schema for language.

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 ("Shows a building model in 3D inside the conversation") and enumerates the interactive capabilities: rotate, per-storey view, cut-away. It does not explicitly distinguish itself from siblings such as vedutum_model_geometry or vedutum_example_project, so an agent must infer the split between rendering a view and fetching geometry or example data.

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?

Gives a clear selection rule for the optional parameter: omit project_id to show the built-in example house with no account, supply it to view a project of the connected account. It stops short of naming alternatives to use instead (e.g. when geometry data rather than a visual is wanted), so there is context but no explicit exclusions.

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