Skip to main content
Glama
JigSawFr

eurodns-mcp

by JigSawFr
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

Get an invoice profile, or search them

eurodns_invoice_profile_get
Read-onlyIdempotent

Get a customer's invoice profile by ID, or search by name, company, country, and status to find the correct billing profile. Use the returned ID to retrieve invoices.

Instructions

Returns one customer invoice profile — the billing name, address and VAT details invoices are issued to — by id, or searches the account’s profiles by name, company, country and status when id is omitted. Use it to find the id a profile is billed under, then pass that id as cipId to eurodns_invoice_get to list its invoices.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoNumeric id of the invoice profile to return in full. Omit it to search the account’s profiles with the filters below.
cityNoThe invoice profile city.
pageNo1-based page number. There is no page meaning everything: walk pages until a short one comes back.
sizeNoResults per page, 1 to 500. A wide page is truncated by the character limit, so prefer a filter to a large size.
emailNoThe invoice profile email address.
activeNoThe invoice profile active status. Inactive invoice profiles are not selectable by users when placing orders and should only be used for keeping track of past invoices.
lastNameNoThe invoice profile last name.
firstNameNoThe invoice profile first name.
sortFieldNoResult field to sort on, spelled as in the response items. Unsorted when omitted.
sortOrderNoASC or DESC; only read with sortField.
companyNameNoThe invoice profile company name.
countryCodeNoThe invoice profile country code.
profileNameNoThe display name of the invoice profile.
defaultProfileNoThe invoice profile default status.
termMatchingModeNoThe match mode to apply on the given `profile-name`, `first-name`, `last-name`, `company-name`, `city` or `email` field.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesResponse body as returned by the API.
statusYesUpstream HTTP status code.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed17 schema fields changedv0.10.0
    • addedInput schema / properties / active
      Added value: +{
+  "description": "The invoice profile active status. Inactive invoice profiles are not selectable by users when placing orders and should only be used for keeping track of past invoices.",
+  "type": "boolean"
+}
    • removedInput schema / properties / cipId
      Removed value: -{
-  "maximum": 9007199254740991,
-  "minimum": -9007199254740991,
-  "type": "integer"
-}
    • addedInput schema / properties / city
      Added value: +{
+  "description": "The invoice profile city.",
+  "type": "string"
+}
    • addedInput schema / properties / companyName
      Added value: +{
+  "description": "The invoice profile company name.",
+  "type": "string"
+}
    • addedInput schema / properties / countryCode
      Added value: +{
+  "description": "The invoice profile country code.",
+  "type": "string"
+}
    • addedInput schema / properties / defaultProfile
      Added value: +{
+  "description": "The invoice profile default status.",
+  "type": "boolean"
+}
    • addedInput schema / properties / email
      Added value: +{
+  "description": "The invoice profile email address.",
+  "type": "string"
+}
    • addedInput schema / properties / firstName
      Added value: +{
+  "description": "The invoice profile first name.",
+  "type": "string"
+}
    • addedInput schema / properties / id
      Added value: +{
+  "description": "Numeric id of the invoice profile to return in full. Omit it to search the account’s profiles with the filters below.",
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}
    • addedInput schema / properties / lastName
      Added value: +{
+  "description": "The invoice profile last name.",
+  "type": "string"
+}
    • addedInput schema / properties / page
      Added value: +{
+  "description": "1-based page number. There is no page meaning everything: walk pages until a short one comes back.",
+  "maximum": 9007199254740991,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / profileName
      Added value: +{
+  "description": "The display name of the invoice profile.",
+  "type": "string"
+}
    • addedInput schema / properties / size
      Added value: +{
+  "description": "Results per page, 1 to 500. A wide page is truncated by the character limit, so prefer a filter to a large size.",
+  "maximum": 500,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / sortField
      Added value: +{
+  "description": "Result field to sort on, spelled as in the response items. Unsorted when omitted.",
+  "type": "string"
+}
    • addedInput schema / properties / sortOrder
      Added value: +{
+  "description": "ASC or DESC; only read with sortField.",
+  "enum": [
+    "ASC",
+    "DESC"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / termMatchingMode
      Added value: +{
+  "description": "The match mode to apply on the given `profile-name`, `first-name`, `last-name`, `company-name`, `city` or `email` field.",
+  "enum": [
+    "EQUALS",
+    "NOT_EQUALS",
+    "CONTAINS",
+    "STARTS_WITH",
+    "ENDS_WITH",
+    "NOT_CONTAINS"
+  ],
+  "type": "string"
+}
    • removedInput schema / required
      Removed value: -[
-  "cipId"
-]
  2. First observedv0.9.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds useful behavioral context beyond annotations: the tool switches between fetching a single profile and searching depending on whether id is present, and it explains the downstream invoice-listing workflow. No contradiction exists.

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 carry the full purpose, the search behavior, the returned data scope, and the intended downstream use. Information is front-loaded and no words are wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the rich input schema, output schema, and annotations, the description fully covers what an agent needs to select and call this tool correctly. It explains the id-vs-search branching, the billing profile semantics, and how results connect to eurodns_invoice_get.

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 description coverage is 100%, so the baseline is already 3. The description adds genuine semantic value by explaining that omitting id triggers the search path and that the returned profile id feeds into eurodns_invoice_get, which clarifies the central decision logic of the tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: it returns one customer invoice profile by id, or searches profiles by filters when id is omitted. It also names the specific billing data returned (name, address, VAT details), which clearly distinguishes this tool from generic profile or domain tools in the sibling list.

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?

The description gives clear context for when to use this tool: to locate the profile id a customer is billed under and then pass that id as cipId to eurodns_invoice_get. It explains the dual mode (get by id vs search when id is omitted) but does not explicitly name alternative search tools or state when not to use it, so it stops short of a perfect score.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/JigSawFr/eurodns-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server