Skip to main content
Glama
gabrielnika

mydata-mcp

by gabrielnika

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MYDATA_ENVNoEnvironment: production (default) or sandboxproduction
MYDATA_USER_IDYesAADE user id
MYDATA_SUBSCRIPTION_KEYYesAADE subscription key

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

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
extensions
{
  "io.modelcontextprotocol/ui": {}
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_received_documentsA

Fetch documents RECEIVED by your business (e.g. supplier invoices) from myDATA.

get_transmitted_documentsA

Fetch documents ISSUED by your business (sales invoices, receipts) from myDATA.

get_income_summaryA

Fetch INCOME bookings per classification from myDATA e-books (RequestMyIncome).

Each record aggregates documents per counterparty/type/classification with net, VAT, and gross totals. Classification codes are decoded to labels.

get_expense_summaryA

Fetch EXPENSE bookings per classification from myDATA e-books (RequestMyExpenses).

Each record aggregates documents per counterparty/type/classification with net, VAT, and gross totals. Classification codes are decoded to labels.

Prompts

Interactive templates invoked by user choice

NameDescription
monthly_reviewProduce a monthly business review from myDATA data.

Resources

Contextual data attached and managed by the client

NameDescription
invoice_typesAll myDATA document type codes (1.1-17.6) with English and Greek labels.
vat_categoriesmyDATA VAT category codes with rates and labels.
classificationsmyDATA income/expense classification categories and common E3 types.

TDQS

A4.2/5.0

Scored across 4 tools

Disambiguation5/5

Each tool targets a clearly distinct resource: received vs transmitted documents, and income vs expense summaries. No overlap in purpose or data returned.

Naming Consistency5/5

All tool names follow the same get_[adjective]_[noun] pattern, with consistent snake_case and clear modifiers. The naming style is uniform and predictable.

Tool Count5/5

Four tools is well within the ideal 3-15 range, and each covers a distinct core query type for the myDATA domain. No redundant tools are present.

Completeness4/5

The read-only surface logically covers documents and summaries for both income and expenses. Major gaps are unlikely, though individual document retrieval or mutation tools are absent, which may not be required for this reporting-oriented server.

Maintenance

ActivitySlowing
ResponsivenessNo issues