Skip to main content
Glama

How to start a project in VEDUTUM

vedutum_get_started
Read-onlyIdempotent

Says where to begin. Without a connected account: the links to open one or sign in, and the four steps from floor plan to share page. With the account connected: how many projects it has and, while it has none, the usual first steps in order (the example house in 3D with vedutum_view_model, then reading a floor plan of one’s own). Use when someone has just connected VEDUTUM, asks what it can do, or wants to try it with their own plan. Creates nothing.

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

Input Schema

NameRequiredDescriptionDefault
languageNoLanguage of the answer: "de" (German) or "en" (English). Default "de".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/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 behavioural context: output varies by account state (sign-in links and four steps vs. project count and ordered first steps), and 'Creates nothing' confirms no side effects. It stops short of describing response format or length, which keeps it below a 5.

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 opening sentence is front-loaded and the two account states are laid out in a clear parallel structure. The second clause is long and slightly convoluted, but every sentence contributes scoping information rather than filler.

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 no output schema, the description must explain what comes back, and it does so branch by branch for both the unauthenticated and authenticated cases. For a zero-required-parameter onboarding tool this is essentially complete, missing only detail on response size or formatting.

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?

There is a single optional parameter with 100% schema description coverage and an enum with a documented default ('de'), so the schema carries the full burden. The description says nothing about language selection, leaving it entirely to the schema, which is the expected baseline at full coverage.

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 states the resource clearly ('Says where to begin') and enumerates the exact content returned in each account state, so an agent knows this is an onboarding/guidance tool rather than a data operation. It differentiates itself from siblings only implicitly by naming vedutum_view_model as a suggested next step rather than contrasting behaviour.

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?

It gives concrete triggers: 'when someone has just connected VEDUTUM, asks what it can do, or wants to try it with their own plan'. That is a clear usage context with no explicit exclusions, and the closing 'Creates nothing' steers the agent away from treating it as a project-creation tool.

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