Skip to main content
Glama

Show the example project

vedutum_example_project
Read-onlyIdempotent

Returns VEDUTUM’s example project „Haus Lindenweg“ (a fictional study): the share page a client receives, a step-by-step demo and five pictures from plan to finished visualisation, with captions. Use when someone wants to see what the result looks like.

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

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

A4.1/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive, closed-world operation. The description adds useful behavioral context by disclosing the returned content: a client share page, a step-by-step demo, and five captioned pictures from plan to visualization. It does not cover language behavior or output format details, but with annotations carrying the safety profile, this is adequate.

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?

The description is front-loaded with the concrete return contents and then gives the usage condition in a second short sentence. It is appropriately sized for a simple read-only example-project tool and contains no wasted wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simple one-parameter, read-only nature of the tool and the absence of an output schema, the description is complete enough. It explains both what the tool returns and the situation in which an agent should call it.

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?

The input schema fully documents the single language parameter, including the de/en enum and default 'de'. The description adds no parameter-specific meaning beyond that, so the schema-coverage baseline of 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?

The description states a specific resource and scope: it returns VEDUTUM's example project 'Haus Lindenweg', a fictional study containing a share page, a step-by-step demo, and five captioned pictures. This is clearly more than a restatement of the name, but it does not explicitly differentiate itself from related siblings such as get_started, get_project, or view_model.

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?

The description gives a clear usage condition: 'Use when someone wants to see what the result looks like.' It does not specify when not to use it or name alternative tools, so it falls short of the explicit alternative-routing guidance that would merit a 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