Skip to main content
Glama
g-digital-by-Garrigues

EAD Factory MCP Server

Official
by g-digital-by-Garrigues
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

notification_certificate_pdf_url_get

Read-onlyIdempotent

Retrieves the download URL for a previously generated notification delivery certificate. Requires: notification_certificate_generate → reportId.

Instructions

Retrieves the download URL for a previously generated notification delivery certificate. Requires: notification_certificate_generate → reportId.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
reportIdYesMANDATORY. UUID of the report.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.4.0
    • removedOutput schema / properties / data / allOf
      Removed value: -[
-  {
-    "additionalProperties": {},
-    "properties": {
-      "empty": {
-        "type": "boolean"
-      }
-    },
-    "type": "object"
-  },
-  {
-    "additionalProperties": {},
-    "properties": {
-      "empty": {
-        "type": "boolean"
-      }
-    },
-    "type": "object"
-  },
-  {
-    "additionalProperties": {},
-    "properties": {
-      "empty": {
-        "type": "boolean"
-      }
-    },
-    "type": "object"
-  },
-  {
-    "additionalProperties": {},
-    "properties": {
-      "empty": {
-        "type": "boolean"
-      }
-    },
-    "type": "object"
-  }
-]
    • addedOutput schema / properties / data / properties
      Added value: +{
+  "empty": {
+    "type": "boolean"
+  }
+}
    • addedOutput schema / properties / data / type
      Added value: +"object"
  2. First observedv1.3.1

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering the safety and idempotency profile. The description adds the prerequisite context about needing a previously generated certificateID, which is useful. However, it doesn't disclose details like whether the URL expires or requires authentication, but with annotations covering the main traits, a 3 is appropriate.

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?

The description is extremely concise: one sentence for purpose and one for the prerequisite. It front-loads the verb and resource, and every word adds value. The prerequisite is clearly signaled with a pipe and arrow.

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?

For a simple one-parameter getter with a well-documented schema and comprehensive annotations, the description covers the essential prerequisite and purpose. The output schema and annotations handle the rest, so 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?

The schema provides full coverage (100%) with a detailed description for reportId, including format and mandatory status. The description only mentions reportId in the prerequisite context, not adding new semantics beyond what the schema already states. Thus, baseline 3 is correct.

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 clearly states the tool retrieves a download URL for a notification delivery certificate, specifying the exact resource and action. It distinguishes itself from siblings like notification_certificate_generate by focusing on retrieval of an already-generated certificate.

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 states the prerequisite: 'Requires: notification_certificate_generate → reportId.' This tells the agent when to use this tool (after generation) and implies not to use it before that step. It also contrasts with sibling tools like evidence_download_url_create that generate URLs for other resources.

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

Deploy Server

Other Tools