Skip to main content
Glama

signvoy_get_signed_pdf_url

Read-only

Return a short-lived (10 min) presigned URL to download the certified signed PDF for a completed document. Only available when status is 'completed'. Do not cache — request a fresh URL each time.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "document_id": "<document_id>"
    },
    "name": "signvoy_get_signed_pdf_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
document_idYesDocument UUID from signvoy_list_documents. Must be in 'completed' status.
workspace_idNoTarget workspace UUID. Safe to omit only when the user belongs to exactly one workspace; required otherwise, and omitting it then fails with the list of candidates. Call signvoy_list_workspaces to find it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses the URL's 10-minute lifetime, that it is presigned, and that it must not be cached — freshness and expiry semantics an agent could not infer from the schema. The only minor omission is the exact failure behavior when the document is not completed.

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?

Three short sentences, front-loaded with the return value, then the availability constraint, then the caching rule. No sentence is redundant and nothing is buried.

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 two-parameter read-only tool with no output schema, the description covers what is returned (a presigned URL), how long it lives, and when it is callable. Nothing an agent needs in order to invoke it correctly 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%, and the schema already documents both document_id (UUID from signvoy_list_documents, must be completed) and workspace_id (including the multi-workspace failure mode and pointer to signvoy_list_workspaces). The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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 gives a specific verb and resource: 'Return a short-lived (10 min) presigned URL to download the certified signed PDF.' It also states the eligibility condition ('Only available when status is \'completed\''), which cleanly separates it from the status, listing, and reminder siblings.

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?

It clearly states the precondition for use (document status must be 'completed') and an operational rule ('Do not cache — request a fresh URL each time'). It stops short of naming an alternative action, such as checking status via signvoy_get_document_status first or what to do when the document is not yet completed.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources