Skip to main content
Glama
davidkotler

icount-mcp

by davidkotler
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Get document PDF URL

icount_get_document_url
Read-onlyIdempotent

Generate a viewable and printable PDF URL for an existing iCount document. Provide the document type and number to get the link, with options for language, watermark, and tracking.

Instructions

Get a viewable/printable URL (PDF) for an existing document.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
langNoUI language for the request (default he)
docnumYesThe document number as shown in iCount
docLangNoLanguage the document itself is rendered in
doctypeYes
emailToNoLog this address against the generated link, for tracking
hideIlsNoHide ILS-equivalent prices (foreign-currency docs only)
originalNoOriginal vs. copy watermark (default true = original)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.3.2
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / docnum / anyOf
      Added value: +[
+  {
+    "minLength": 1,
+    "type": "string"
+  },
+  {
+    "exclusiveMinimum": 0,
+    "maximum": 9007199254740991,
+    "type": "integer"
+  }
+]
    • addedInput schema / properties / docnum / description
      Added value: +"The document number as shown in iCount"
    • removedInput schema / properties / docnum / type
      Removed value: -[
-  "string",
-  "number"
-]
    • addedInput schema / properties / emailTo / pattern
      Added value: +"^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"
  2. First observedv0.2.0

TDQS

A4/5.0
Behavior4/5

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

With annotations already providing readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, the description adds useful behavioral context by clarifying that the operation returns a viewable/printable PDF URL rather than a document payload or a rendered PDF file. It also implicitly confirms no write side-effects are involved, consistent with the annotations.

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 a single clear sentence with no filler. It front-loads the core action ('Get'), the resource ('URL (PDF)'), and the condition ('existing document'), earning every word.

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 rich schema (7 parameters, enums, high coverage) and the presence of safety annotations, the description covers the essential return nature (PDF URL) and scope (existing document) without needing to restate schema details. It would benefit from mentioning whether the URL is temporary or persistent, but the core knowledge needed for correct selection and invocation is present.

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 86%, so the input schema already documents most parameters. The description itself does not add parameter-level meaning beyond indicating the output is a PDF URL, but with such high schema coverage, that is acceptable at the baseline level.

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 ('Get') and resource ('viewable/printable URL (PDF) for an existing document'), clearly distinguishing it from sibling tools like icount_get_document, which returns document data rather than a PDF URL. The phrase 'existing document' also narrows the scope and prevents confusion with create/update tools.

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

Usage Guidelines3/5

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

Usage context is implied: use this when you need a PDF URL for an already-existing document. However, the description does not explicitly state when not to use it or name alternatives, so an agent must infer the choice from sibling tool names and context signals rather than receiving direct routing guidance.

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