Skip to main content
Glama

getecoback-raumklima

eco_raeumdaten_quellenangabe

Read-only

Eine zitierfähige Quellen- und Versionsangabe für EcoBack-Dimensionierungsdaten erzeugen — Create a ready-to-cite attribution for EcoBack’s open sizing dataset.

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": {
      "metric": "<metric>",
      "angepasst": "<angepasst>"
    },
    "name": "eco_raeumdaten_quellenangabe"
  }
}

Input Schema

NameRequiredDescriptionDefault
metricYesGenutzte Datenreihe.
angepasstYesWurden die Werte für die eigene Publikation angepasst?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. Beyond that, the description adds nothing: it does not state what the produced citation looks like, whether it includes a version string or license note, or how the result changes based on input. For a generator tool with no output schema, that is a real gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

A single front-loaded sentence is efficient in structure, but it is given twice in German and English, which is redundant rather than additive. No wasted clauses beyond that duplication.

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

Completeness2/5

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

This is the sole output-producing tool in view and there is no output schema, so the description is the only place the citation format, language, and version handling could be described, and it omits all of it. The only added information over the schema is the dataset's name.

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 both parameters are documented in structured form and the baseline of 3 applies. The description could have added value by explaining why 'angepasst' matters (e.g., whether the citation is marked as adapted), but it does not.

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 names a specific verb and artifact: generating a citable source-and-version attribution for the EcoBack sizing dataset. An agent can tell this is a metadata/citation producer rather than a data-query tool, though it does not differentiate itself from any sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use it, when not to, or what alternatives exist for citation needs. It also does not say whether it should be called after retrieving sizing data, or whether it can stand alone.

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