Skip to main content
Glama
JigSawFr

eurodns-mcp

by JigSawFr
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

Get an SSL subscription, or search them

eurodns_ssl_get_subscription
Read-onlyIdempotent

Retrieve a specific SSL subscription by ID, or search by status, common name, SAN, or renewability to get certificates, expiry dates, and certificate IDs for further API calls.

Instructions

Returns one SSL subscription with its certificates and their expiry by id, or searches SSL subscriptions by status, common name, SAN or renewability when id is omitted. Use it to find the certificateId that eurodns_ssl_get_certificate and eurodns_ssl_get_validation need; every product at once is eurodns_subscription_search.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoNumeric id of the SSL subscription to return with its certificates. Omit it to search SSL subscriptions with the filters below.
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.
sanNameNoSubject Alternative Name exactly as it appears on the certificate, e.g. www.example.com, from eurodns_ssl_get_certificate.
renewableNoThe renewal capacity of the SSL subscription.
sortFieldNoResult field to sort on, spelled as in the response items. Unsorted when omitted.
sortOrderNoASC or DESC; only read with sortField.
commonNameNoThe common name of an SSL certificate of the subscription.
subscriptionStatusNoKeep only subscriptions in this lifecycle status, e.g. ACTIVE, TO_RENEW or PROVISIONING. Omit for every status.

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. Changed11 schema fields changedv0.10.0
    • addedInput schema / properties / commonName
      Added value: +{
+  "description": "The common name of an SSL certificate of the subscription.",
+  "type": "string"
+}
    • addedInput schema / properties / id
      Added value: +{
+  "description": "Numeric id of the SSL subscription to return with its certificates. Omit it to search SSL subscriptions with the filters below.",
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}
    • 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 / renewable
      Added value: +{
+  "description": "The renewal capacity of the SSL subscription.",
+  "type": "boolean"
+}
    • addedInput schema / properties / sanName
      Added value: +{
+  "description": "Subject Alternative Name exactly as it appears on the certificate, e.g. www.example.com, from eurodns_ssl_get_certificate.",
+  "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"
+}
    • removedInput schema / properties / subscriptionId
      Removed value: -{
-  "maximum": 9007199254740991,
-  "minimum": -9007199254740991,
-  "type": "integer"
-}
    • addedInput schema / properties / subscriptionStatus
      Added value: +{
+  "description": "Keep only subscriptions in this lifecycle status, e.g. ACTIVE, TO_RENEW or PROVISIONING. Omit for every status.",
+  "enum": [
+    "ACTIVE",
+    "TO_RESTORE",
+    "TO_RENEW",
+    "TO_DELETE",
+    "PENDING_RENEW",
+    "PENDING_RENEW_DOWNGRABLE",
+    "UPGRADE_QUANTITY",
+    "PENDING_UPGRADE_PRODUCT",
+    "HOLD",
+    "PENDING_DOWNGRADE_PRODUCT",
+    "MIGRATED",
+    "PENDING_REACTIVATE",
+    "PROVISIONING"
+  ],
+  "type": "string"
+}
    • removedInput schema / required
      Removed value: -[
-  "subscriptionId"
-]
  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?

The readOnly/openWorld/idempotent annotations already establish the safety profile, so the description only needs to add behavioral context beyond them. It adds that the result includes certificates and their expiry and that the tool either returns one subscription or searches, which is useful. It does not fully describe pagination or output shape, but the output schema and detailed parameter descriptions cover those.

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 dense sentences front-load the central dual behavior and follow with a practical routing hint. No words are wasted, and the description earns each clause while remaining readable.

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, complete annotations, and presence of an output schema, the description provides all additional context an agent needs: when to use it, how it differs from siblings, and what data it returns. Nothing critical is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/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 3 and the schema carries the parameter documentation burden. The description summarizes the filter dimensions (status, common name, SAN, renewability) and the id-omission rule, but adds little beyond what the parameter descriptions already state. It does not introduce new parameter meaning.

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 names a specific resource (SSL subscriptions), the verb (returns/searches), and the dual by-id lookup versus filter-based search behavior. It also distinguishes itself from sibling tools by noting that eurodns_subscription_search covers every product, so an agent can select it correctly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly says when to use the tool: to find the certificateId needed by eurodns_ssl_get_certificate and eurodns_ssl_get_validation. It also gives an explicit alternative, eurodns_subscription_search, for all-product searches, and clarifies that omitting id triggers the search variant.

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