Skip to main content
Glama

List my VEDUTUM projects

vedutum_list_projects
Read-onlyIdempotent

Lists the projects in the connected VEDUTUM account with id, client, whether the floor plan has been read, last change, and the points left. Use first when the person talks about one of their projects, to find its id.

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

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of projects, default 20, newest change first
statusNoWhich projects: "active" (default), "archived" or "all"
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 value the annotations cannot: it discloses the shape of each returned project record, which matters because there is no output schema. It does not mention ordering or truncation behavior in the prose, but ordering is already in the schema.

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 sentences, front-loaded with what the tool returns and followed by the routing cue. The field enumeration is slightly list-like but each item carries information an agent needs to pick the right id. No redundant restatement of the title.

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, enumerating the returned fields is the key completeness contribution and it is present. All three parameters are schema-documented, so nothing critical is missing, though terms like "points left" are left undefined and there is no note on whether results are truncated.

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 limit, status and language are already fully documented with defaults and enum meanings. The description adds nothing about filtering, paging or the language parameter, so the baseline 3 applies.

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 ("Lists the projects in the connected VEDUTUM account") and enumerates the returned fields (id, client, floor-plan read state, last change, points left). It implicitly distinguishes itself from vedutum_get_project by positioning itself as the lookup-first step to obtain an id, though it never names that sibling.

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?

Explicit when-to-use: "Use first when the person talks about one of their projects, to find its id." That gives the agent a clear trigger and sequencing rule. It does not name an alternative tool or state when not to use it, so it stops short of full routing guidance.

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