Skip to main content
Glama

Search VEDUTUM articles, services and feature pages

vedutum_search_knowledge
Read-onlyIdempotent

Searches VEDUTUM’s published articles, service pages and feature documentation (German or English) and returns titles, short answers and links. Use for questions about architectural visualisation: floor plan to 3D, rendering costs and resolutions, IFC and CAD formats, sign-off with clients, AI labelling of images.

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": {
      "query": "<query>"
    },
    "name": "vedutum_search_knowledge"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of results, default 5
queryYesSearch words, e.g. "Grundriss in 3D umwandeln" or "rendering resolution print"
languageNoLanguage of the answer: "de" (German) or "en" (English). Default "de".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

The annotations already declare readOnly, idempotent, non-destructive and openWorldHint=false, so the safety profile is fully covered. The description adds genuinely non-structured context: it discloses the return shape ('titles, short answers and links') and that the corpus is published, bilingual content. It omits ranking behaviour and result-count semantics, so not quite 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero waste, front-loaded with the resource and scope before the usage topics. The topic list is compact and every item maps to a real user question rather than padding.

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 does so ('titles, short answers and links'), which is the key missing piece for a search tool. Limits and enum values are handled by the schema, so the only remaining gap is ranking or result-count behaviour, which is minor for an idempotent read.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the schema already explains query, limit and the de/en enum, so the baseline would be 3. The description earns a small lift by stating the corpus is 'German or English', reinforcing what the language parameter selects between and hinting that query terms may be in either language.

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?

The description opens with a specific verb and resource ('Searches VEDUTUM's published articles, service pages and feature documentation') and scopes it by language and return content. It is also unambiguous against the siblings, all of which are action tools (create_project, check_floor_plan, view_model) rather than retrieval, so an agent can route a knowledge question here without opening any schema.

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?

'Use for questions about architectural visualisation' plus a concrete topic list (floor plan to 3D, rendering costs, IFC/CAD, sign-off, AI labelling) gives an explicit trigger condition. It stops short of naming when NOT to use it or pointing at a specific alternative, which keeps it below 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