Skip to main content
Glama

Create a project

vedutum_create_project

Creates a new, empty project in the connected account, optionally with the client and the site address (looked up for sun and surroundings). Returns its id and the link where the floor plan can be uploaded. Costs no points.

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": {
      "title": "<title>"
    },
    "name": "vedutum_create_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesProject name, e.g. "Haus Berger" or "Wohnanlage Lindenweg"
addressNoSite address, optional, e.g. "Lindenweg 7, 8010 Graz"
languageNoLanguage of the answer: "de" (German) or "en" (English). Default "de".
client_nameNoClient or owner, optional

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare a non-read-only, non-idempotent, open-world write, so the bar is lower; the description still adds real behavior: the new project starts empty, the address triggers a lookup used for sun and surroundings, and the call returns an id plus the floor-plan upload link. It also discloses that the operation consumes no points, which is valuable context for a metered product. It does not state whether repeated calls create duplicate projects (which the non-idempotent hint implies) or any account/permission requirements.

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?

Three short sentences, front-loaded with the action, then the optional inputs, then the return value and cost. Every clause carries distinct information (creation scope, address lookup purpose, return payload, cost) with no 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 correctly compensates by naming what comes back (id and upload link), and it covers cost and the side effect of address lookup. For a simple 4-parameter creation tool this is nearly complete; a line about non-idempotency or the prerequisite that the floor plan must be uploaded afterward would close the remaining 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 description coverage is 100%, so the schema already documents all four parameters, making 3 the baseline. The description adds modest extra meaning by explaining that 'address' is not just metadata but is geocoded and used for sun and surroundings analysis, and that client_name and address are optional; it adds nothing for title or language beyond the schema, including the 'de' default already covered in the enum description.

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 concrete verb and resource: 'Creates a new, empty project in the connected account', with the qualifier 'empty' making clear this is creation rather than reuse of an existing project (contrasting implicitly with vedutum_get_project / vedutum_list_projects). It never names a sibling or says which one it replaces, so it stops short of full differentiation.

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?

Usage is implied rather than stated: the returned upload link signals this is the entry point before floor-plan work, and 'Costs no points' hints at a contrast with point-consuming operations like vedutum_estimate_points or vedutum_add_solar. There are no explicit when-to-use / when-not-to-use rules or prerequisites (e.g. what to do if a project already exists).

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