Skip to main content
Glama

Project details: storeys, rooms and areas

vedutum_get_project
Read-onlyIdempotent

Returns one project of the connected account: the state of each floor plan reading (also while it runs), storeys, rooms with their approximate areas, outline area per storey and in total, windows and doors, roof, facade and style, solar modules, surroundings, share link and approval, number of images, and the link into the app. Use after vedutum_read_floor_plan to see the result, and for questions about areas or rooms.

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": {
      "project_id": "<project_id>"
    },
    "name": "vedutum_get_project"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds genuinely new behavioral context beyond that: it returns 'the state of each floor plan reading (also while it runs)', telling the agent this tool doubles as a status/polling endpoint during processing. It does not cover error behavior or whether partial results appear while a reading is incomplete.

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?

Front-loaded with the core verb and resource, with usage guidance in a second sentence. The long comma-separated return enumeration is dense but each item tells the agent what data is available, which matters because there is no output schema. Minor redundancy with the title's 'storeys, rooms and areas'.

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 carries the burden of describing returns, and it does so thoroughly while also flagging the in-progress reading state. It is nearly complete for an agent's needs; only error/empty-state behavior and whether results are cached per reading are unaddressed.

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%, with project_id documented as coming from vedutum_list_projects and language documented with its enum and default. The description adds no parameter-level meaning beyond that (it never mentions project_id or the language switch), so the baseline of 3 applies.

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?

States a specific verb and resource ('Returns one project of the connected account') and immediately scopes it against the plural sibling by saying 'one project'. The enumeration of what is returned (storeys, rooms with approximate areas, windows and doors, roof, facade, solar modules, share link) makes the tool unmistakable versus vedutum_list_projects.

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?

Explicitly names a predecessor and a use case: 'Use after vedutum_read_floor_plan to see the result, and for questions about areas or rooms.' That is clear when-to-use guidance. It stops short of exclusions (e.g., don't use this just to get project names — use vedutum_list_projects), so it is not a full 5.

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