Skip to main content
Glama

Assinafy MCP Server

by br.com.assinafy.mcp
OverviewDiscussionsAdmin

Download a document or page

assinafy_download_document
Read-only

Retrieve bytes only when needed. artifact downloads original (default), certificated, certificate-page, pades or bundle; wait for certificated status and artifact availability before downloading the signed PDF. page downloads a preview using a page_id returned by find_documents. Results contain base64 bytes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesChoose exactly one action; supply only its arguments.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / oneOf
      Added value: +[
+  {
+    "additionalProperties": false,
+    "description": "Download a document artifact as base64.",
+    "properties": {
+      "action": {
+        "enum": [
+          "artifact"
+        ],
+        "type": "string"
+      },
+      "artifact": {
+        "description": "original (default), certificated, certificate-page, pades, or bundle",
+        "type": "string"
+      },
+      "document_id": {
+        "description": "unique document ID",
+        "type": "string"
+      }
+    },
+    "required": [
+      "document_id",
+      "action"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "description": "Download the rendered image of a specific document page.",
+    "properties": {
+      "action": {
+        "enum": [
+          "page"
+        ],
+        "type": "string"
+      },
+      "document_id": {
+        "description": "Document ID.",
+        "minLength": 1,
+        "type": "string"
+      },
+      "page_id": {
+        "description": "The page ID.",
+        "minLength": 1,
+        "type": "string"
+      }
+    },
+    "required": [
+      "document_id",
+      "page_id",
+      "action"
+    ],
+    "type": "object"
+  }
+]
    • addedInput schema / properties / action
      Added value: +{
+  "description": "Choose exactly one action; supply only its arguments.",
+  "enum": [
+    "artifact",
+    "page"
+  ],
+  "type": "string"
+}
    • removedInput schema / properties / artifact
      Removed value: -{
-  "description": "original (default), certificated, certificate-page, pades, or bundle",
-  "type": "string"
-}
    • removedInput schema / properties / document_id
      Removed value: -{
-  "description": "unique document ID",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "document_id"
-]New value: +[
+  "action"
+]
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": false,
-  "properties": {
-    "artifact": {
-      "description": "which artifact was downloaded",
-      "type": "string"
-    },
-    "base64": {
-      "description": "base64-encoded artifact bytes",
-      "type": "string"
-    },
-    "document_id": {
-      "description": "the document the artifact belongs to",
-      "type": "string"
-    }
-  },
-  "required": [
-    "document_id",
-    "artifact",
-    "base64"
-  ],
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "artifact": {
+      "description": "which artifact was downloaded",
+      "type": "string"
+    },
+    "base64": {
+      "description": "base64-encoded artifact bytes",
+      "type": "string"
+    },
+    "document_id": {
+      "description": "the document the artifact belongs to",
+      "type": "string"
+    }
+  },
+  "required": [
+    "document_id",
+    "artifact",
+    "base64"
+  ],
+  "type": "object"
+}
  4. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations include readOnlyHint=true (no mutation) and openWorldHint=true (may perform external calls). The description does not contradict these but adds behavioral context: it warns to wait for certificated status and artifact availability before downloading, and mentions the output format (base64 bytes). It does not disclose potential latency or external dependencies, but the annotation covers the key safety aspects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise (two sentences) and front-loads the core purpose ('Retrieve bytes only when needed') before elaborating on actions. It efficiently packs important conditions (wait for status, availability) and output format (base64) without redundancy.

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

Completeness4/5

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

Given the tool's complexity (oneOf schema, multiple artifact types, dependency on other tools), the description covers the essential usage prerequisites and output. The schema is rich, so the description doesn't need to explain return values. No significant gaps identified for an agent to select and invoke this tool correctly.

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%, with detailed parameter descriptions for action, artifact, page_id, and document_id. The description reinforces key semantics (e.g., artifact options are already in schema, but description adds 'default' for original). This adds marginal value beyond the schema, hence baseline 3 is appropriate.

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's purpose: downloading documents or pages. It distinguishes between artifact and page downloads, listing specific artifact types and the relationship between page downloads and find_documents. This differentiates it from sibling tools like verify or prepare.

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 provides clear guidance on when to use this tool: 'Retrieve bytes only when needed' and specifies the prerequisites for each action (wait for certificated status, use page_id from find_documents). It does not explicitly exclude alternatives, but given the tool's unique role among siblings (download vs. verify, delete, etc.), the context is sufficient.

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

All Assinafy MCP Server toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources