Skip to main content
Glama
Sign In
Förderdatenbank MCP

Förderdatenbank MCP

by New-Life-Digital
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Förderprogramme suchen

foerderprogramme_suchen
Read-onlyIdempotent

Search German federal, state, and EU funding programs by German keywords and filters like region, sector, funding type, and applicant group to find suitable grants, loans, and program links.

Instructions

Durchsucht die Förderdatenbank des Bundes nach passenden Förderprogrammen von Bund, Ländern und EU. Liefert Treffer mit ID, Kurzbeschreibung, Förderart, Gebiet und Link zur Originalseite. Suchbegriffe auf Deutsch, am besten so, wie sie in Förderrichtlinien stehen (z. B. „Digitalisierung“, „Energieeffizienz“, „Existenzgründung“, „Innovationsgutschein“, „Weiterbildung“). Mit Filtern eingrenzen, vor allem mit dem Bundesland des Standorts. Ohne Suchbegriffe werden alle Programme zu den Filtern geliefert, neueste zuerst.

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": "foerderprogramme_suchen"
  }
}

Input Schema

NameRequiredDescriptionDefault
anzahlNoAnzahl Treffer, Standard 10, höchstens 25
versatzNoFür weitere Seiten: Anzahl zu überspringender Treffer
branchenNoBranche des Unternehmens
bundeslandNoBundesland des Unternehmenssitzes oder Vorhabens. Bundesweite Programme werden mitgeliefert.
foerderartNoz. B. Zuschuss oder Darlehen
foerdergeberNoBund, Land oder EU
suchbegriffeNoFreitext auf Deutsch, z. B. "Digitalisierung Handwerk" oder "Photovoltaik Landwirtschaft"
foerderbereichNoThematischer Förderbereich
foerderberechtigteNoWer antragsberechtigt ist, z. B. Unternehmen oder Existenzgründer/in
unternehmensgroesseNoGröße des antragstellenden Unternehmens
bundesweitEinschliessenNoStandard true. false liefert nur Programme dieses Bundeslandes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and closed-world, so the safety profile is covered. The description adds real context beyond them: the result fields, the default sort order (newest first), and the semantics of an empty query, which meaningfully predict what comes back.

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?

Five short sentences, front-loaded with purpose and return shape, then query syntax, filter advice and the no-query default. Every sentence carries distinct information and none repeats the schema verbatim.

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 11 optional parameters, no required fields and no output schema, the description supplies the missing return-shape and ordering information an agent needs. Minor gaps remain: nothing about paging limits (offset max 2500) or whether a total hit count is returned.

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%, so the baseline is 3, but the description adds genuine meaning on top: query syntax and vocabulary for suchbegriffe with worked examples, and a recommended filtering strategy via Bundesland. It does not touch pagination (anzahl/versatz) or the boolean default, but those are fully documented in the schema.

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: searching the federal funding database (Förderdatenbank des Bundes) for programmes from Bund, Länder and EU, and enumerates the returned fields. It is clear what the tool does, but it never names the sibling tools (foerderprogramm_details, foerderfilter_auflisten), so the agent must infer the division of labour.

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?

Gives concrete usage guidance: German search terms phrased as they appear in funding guidelines, narrow with filters, especially Bundesland, and explicit behaviour when no search terms are supplied (all programmes matching the filters, newest first). It stops short of stating when to prefer the detail tool or the filter-listing tool over this one.

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

Deploy Server

Other Tools