Skip to main content
Glama
Vortiago

MCP Outline Server

by Vortiago
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

get_attachment_url

Read-onlyIdempotent

Resolve an attachment ID to a direct download URL, enabling sharing or fetching of the file by other systems.

Instructions

    Resolve an attachment ID to a downloadable URL.

    Calls attachments.redirect and returns the final URL after the
    redirect. Allows clients/agents to fetch the file themselves.

    Use this tool when you need to:
    - Get a direct URL to download an attachment
    - Share or reference an attachment URL
    - Let another system fetch the file

    Args:
        attachment_id: The attachment UUID

    Returns:
        The redirect URL (signed download URL)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
attachment_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint. The description adds operational context (calls attachments.redirect, returns final URL, allows clients to fetch themselves), which is valuable beyond 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.

Conciseness4/5

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

The description is front-loaded with the purpose and is relatively concise. The bullet list for usage slightly repeats the purpose, but overall it is well-structured and not overly verbose.

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?

Given the low complexity (one parameter, no nested objects, output schema present), the description covers purpose, usage, parameter, and return value completely. No gaps remain.

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

Parameters4/5

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

The description explicitly documents the 'attachment_id' parameter as a UUID, adding semantic meaning beyond the schema's type and title. With 0% schema coverage, this compensates well.

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 resolves an attachment ID to a downloadable URL. It distinguishes from siblings like fetch_attachment by indicating the output is a URL for clients to fetch themselves.

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 lists specific use cases: getting a direct URL, sharing/referencing a URL, or letting another system fetch the file. It provides clear context but does not explicitly mention when not to use it or name alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Vortiago/mcp-outline'

If you have feedback or need assistance with the MCP directory API, please join our Discord server