Förderdatenbank MCP

Details zu einem Förderprogramm

foerderprogramm_details

Read-onlyIdempotent

Retrieve complete details for a funding program by ID, including eligibility, deadlines, application procedure, contacts, links, and guideline excerpts or full text.

Instructions

Liefert alle Angaben zu einem Förderprogramm aus der Förderdatenbank: Zusammenfassung, rechtliche Voraussetzungen, Fristen, Verfahren, Ansprechpartner, Links und einen Auszug der Richtlinie. Mit abschnitt="richtlinie" kommt der Volltext der Förderrichtlinie, lange Richtlinien in Teilen.

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": {
      "id": "<id>"
    },
    "name": "foerderprogramm_details"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	ID aus den Suchergebnissen, z. B. "Land/Baden-Wuerttemberg/bw-innovationsgutscheine-fuer-kleine-und-mittlere"
`teil`	No	Bei abschnitt="richtlinie": welcher Teil, Standard 1
`abschnitt`	No	Standard "uebersicht"

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 9, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, openWorldHint=false), so the description's burden is lighter, and it adds genuinely useful behavioral context: the default returns a condensed overview while the guideline full text is delivered in numbered parts, implying truncation/paging the agent must handle. It does not state what happens for an unknown id or how large a 'Teil' is, but the added value over annotations is real.

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 filler: the primary capability and its returned sections are front-loaded, and the special richtlinie mode follows immediately. Every clause carries information an agent needs.

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 takes on the job of describing return content, and it does so concretely. It is nearly complete for a read-only detail lookup; only edge behavior (invalid id, part count/limits) is left unaddressed, which is minor.

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 all three parameters are already documented, giving a baseline of 3. The description reinforces the abschnitt="richtlinie" toggle and explains why 'teil' exists ('lange Richtlinien in Teilen'), which is mild meaning beyond the schema but not syntax, defaults, or limits the schema lacks.

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-resource pair ('Liefert alle Angaben zu einem Förderprogramm') and enumerates the payload (Zusammenfassung, Voraussetzungen, Fristen, Verfahren, Ansprechpartner, Links, Richtlinien-Auszug), which clearly separates it from foerderprogramme_suchen and foerderfilter_auflisten. It never names those siblings explicitly, so the differentiation is inferable rather than stated.

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?

The second sentence gives a concrete use case for one mode: set abschnitt="richtlinie" to get full guideline text, split into parts when long. There is no explicit routing advice such as 'call this after foerderprogramme_suchen using the returned id' or any stated exclusion — the search-then-detail workflow is only hinted at through the schema's id description, not the tool description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server