Skip to main content
Glama

fs_signed_url

Mint a short-lived signed URL for a file. The URL is fetchable without an API key — the token IS the auth. It suits email attachments, image previews, and "download once" handoffs to recipients without a developer key.

expires_in is in seconds, min 60, max 604800 (7 days), default 3600 (1 hour). After expiry the URL returns 403.

Example:

{ "project_id": "my-saas", "path": "/uploads/invoice-2026.pdf", "expires_in": 86400 }
// Returns: { "url": "https://api.somewhere.cloud/v1/fs-signed/eyJ...", "expires_at": "2026-05-13T..." }

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": {
      "project_id": "<project_id>",
      "path": "<path>"
    },
    "name": "fs_signed_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesFull path with leading slash.
expires_inNoSeconds until URL expires. Min 60, max 604800. Default 3600.
project_idYesProject ID (UUID), subdomain, or slug — resolved server-side, no UUID lookup needed. 'default' also works when the account has exactly one project; multi-project accounts must name one (the error lists them).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only say readOnly=false, idempotent=false, destructive=false. The description adds the crucial behavioral facts: the token itself is the auth so anyone holding the URL can fetch it without an API key, the link stops working after expiry with a 403, and the token lifetime is bounded at 7 days. That is exactly the security and lifecycle context annotations cannot express.

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?

Purpose and auth semantics are front-loaded in the first two sentences, and the range/default line is easy to scan. The expires_in range is repeated from the schema, which is minor waste, and the example block, while useful, adds length.

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?

There is no output schema, and the example return payload ({url, expires_at}) covers that gap. Combined with the auth model, expiry behavior, and parameter limits, an agent has everything needed to call this correctly and explain the result to a user.

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 coverage is 100% and every parameter is already documented, including the expires_in range and default. The description largely restates those constraints; its only addition is the 403-on-expiry consequence, which is modest marginal value over the schema.

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?

The opening sentence names a specific verb and resource: 'Mint a short-lived signed URL for a file.' Combined with the auth model explanation, an agent knows exactly what it produces. It does not explicitly differentiate from the sibling fs_public_url, so the agent must infer the distinction between a signed/expiring URL and a public URL.

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 gives concrete usage context — 'email attachments, image previews, and "download once" handoffs to recipients without a developer key' — which clearly frames when this tool is the right choice. It stops short of naming an alternative (e.g. fs_public_url for non-expiring links) or stating when not to use it.

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