agent-card-starter
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| leistungenB | List the services of the business. Auskunft über die Leistungen des Betriebs. |
| anfrage_anlegenC | Create an inquiry (stub, nothing is stored). Anfrage anlegen (Stub, nichts wird gespeichert). |
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 2 tools
The two tools have clearly distinct purposes: one lists available services, the other creates an inquiry. There is no overlap or ambiguity in selecting between them.
Both names are in German and use snake_case, but they follow different conventions: 'leistungen' is a bare noun while 'anfrage_anlegen' is a verb_noun construction. The mixed style is readable but not predictable.
Two tools is on the thin side for a functional server, even a starter one. The set is not over-scoped, but it feels minimal and close to being too sparse.
The surface lacks basic lifecycle coverage: there is no way to retrieve service details, and the inquiry creation explicitly stores nothing. No update, delete, or persistence operations exist, creating significant dead ends.