Debeka MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| debeka_open_pageA | Opens the Debeka Leistungsauftrag form page in a browser. This tool launches a Chromium browser and navigates to the Debeka form for submitting medical invoices. Args:
Returns: Success message with page title, or error if page couldn't be loaded. Example:
|
| debeka_fill_credentialsA | Fills in all personal data fields on the Debeka Leistungsauftrag form. This tool enters your credentials into the open Debeka form. Make sure to call debeka_open_page first. Args:
Returns: Success message if credentials were entered, or error details. Example: servicenummer="2267092.1", geburtsdatum="25.06.1974", vorname="Jyn", nachname="Schultze-Melling", telefon="+4917672825190" |
| debeka_upload_documentsA | Uploads PDF documents to the Debeka form. This tool uploads one or more PDF files to the Debeka Leistungsauftrag form. Make sure to call debeka_open_page and debeka_fill_credentials first. Args:
Returns: Success message listing uploaded files, or error details. Example: file_paths=["/path/to/invoice1.pdf", "/path/to/invoice2.pdf"] |
| debeka_screenshotA | Takes a screenshot of the current browser page. Useful for verifying the current state of the form before submitting. Args:
Returns: Screenshot saved confirmation or base64 encoded image data. |
| debeka_submitA | Submits the Debeka Leistungsauftrag form. WARNING: This will actually submit the form! Make sure all data is correct first. Returns: Success message if form was submitted, or error details. |
| debeka_closeA | Closes the browser instance. Call this when you're done with the Debeka form to free up resources. Returns: Confirmation that browser was closed. |
| debeka_get_page_infoA | Gets information about the current page structure. Useful for debugging if the form structure has changed. Returns: Page URL, title, and list of form elements found. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool has a clearly distinct role in the form automation workflow: opening, filling, uploading, inspecting, screenshotting, submitting, and closing. There is no meaningful overlap that would cause an agent to select the wrong tool for a given step.
Tool names consistently use snake_case with a debeka_ prefix and mostly follow a verb_noun pattern like debeka_open_page and debeka_fill_credentials. Minor deviations like debeka_submit and debeka_close omit an explicit object, but the pattern remains predictable.
Seven tools is well-scoped for the server's stated purpose of automating a single form submission workflow. Each tool maps to a necessary step or useful utility, with no redundant or excessive additions.
The tool set covers the full lifecycle from opening the page, filling credentials, uploading documents, submitting, and closing the browser, plus debugging aids like screenshot and page info. Minor gaps exist around post-submission verification or waiting for confirmation, but agents can generally complete the core workflow without dead ends.