Skip to main content
Glama
OpenMonetis MCP

OpenMonetis MCP

by Welington98

Link de download do anexo

get_attachment_download_url
Read-onlyIdempotent

Generate a signed, temporary URL to download or view an attachment and return its expiration time. Use the attachment ID to retrieve secure access without exposing permanent links.

Instructions

Gera uma URL assinada e temporária para baixar (ou visualizar) um anexo. Retorna a URL e o instante de expiração.

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": {
      "id": "<id>"
    },
    "name": "get_attachment_download_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
dispositionNoattachment

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world profile, so the safety story is covered. The description adds genuinely useful behavior beyond that: the URL is signed and temporary, and the response carries an expiration timestamp. It still omits the lifetime of the link and whether the URL is single-use or shareable, which are the operationally important details for a signed-URL tool.

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 short sentences with the core capability front-loaded and the return value appended. Nothing is wasted and nothing essential is buried.

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 correctly fills that gap by stating what comes back (the URL and its expiration instant). For a two-parameter read-only tool that is nearly complete; the missing pieces are the URL lifetime and an explicit statement of what the disposition choice does.

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 0%, so the description must carry parameter meaning, and it only partially does: "baixar (ou visualizar)" implicitly maps to the disposition enum (attachment vs inline) without ever naming the parameter, its default of "attachment", or clarifying that "id" is the attachment UUID. The enum values are largely self-explanatory, which limits the practical gap, but the description does not fully compensate.

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 ("Gera") and a specific resource ("uma URL assinada e temporária para baixar (ou visualizar) um anexo"), so an agent immediately knows this produces a temporary access link rather than fetching the file itself. It is clearly distinct from sibling attachment tools (upload/delete), though it never names them explicitly.

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?

The parenthetical "(ou visualizar)" hints that the same tool serves both download and in-browser viewing, which implies when the two modes apply. However, there is no explicit statement of when to choose inline viewing versus attachment download, and no guidance on prerequisites such as the caller needing permission on the attachment.

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