Skip to main content
Glama

Get Pulse Dashboard Attachment Download Url

getPulseDashboardAttachmentDownloadUrl
Read-onlyIdempotent

Mint a short-lived presigned URL to download or preview a file attached to a Duvo Pulse dashboard message. Returns 410 with code sandbox_expired once data retention deleted the dashboard's sandbox, and 404 when the file is otherwise gone.

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": {
      "artifactId": "<artifactId>",
      "attachmentId": "<attachmentId>"
    },
    "name": "getPulseDashboardAttachmentDownloadUrl"
  }
}

Input Schema

NameRequiredDescriptionDefault
artifactIdYes
attachmentIdYesThe attachment to mint a download URL for

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, so the safety profile is covered. The description adds genuinely new behavior: the URL is short-lived/presigned, and it documents the 410 `sandbox_expired` retention case and the 404 missing-file case. It stops short of saying whether the URL is single-use or how long it lives.

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 tight sentences with the core action front-loaded and error semantics trailing. No filler or restatement of the title.

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?

With no output schema, the description should convey the return value; it does so at a high level ('presigned URL') and adds error codes. The remaining gap is the response shape (field name, expiry) and the undocumented artifactId parameter.

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

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%: attachmentId is documented in the schema, but artifactId has no description anywhere. The description does not explain the artifactId/attachmentId relationship or how to obtain either value, so it fails to compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Mint a short-lived presigned URL to download or preview a file attached to a Duvo Pulse dashboard message.' The resource is narrow enough to separate it from getCaseAttachmentDownloadUrl and createPulseDashboardAttachmentUploadUrl, though it never explicitly contrasts itself with those siblings.

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 is implied by 'download or preview a file attached to a ... message', but there is no explicit when-to-use guidance, no statement of prerequisites (e.g. that the caller must already know the artifact and attachment IDs), and no named alternative for related tasks.

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