Skip to main content
Glama
Sign In

Coverlttr

by com.coverlttr
OverviewDiscussionsAdmin

Get User File URL

get_user_file_url
Read-onlyIdempotent

Get a short-lived (2 min) presigned S3 URL to preview or download a previously uploaded user file (CV/resume) by its id from list_user_files.

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": {
      "fileId": "<fileId>"
    },
    "name": "get_user_file_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileIdYesUploaded file id from list_user_files

Output Schema

NameRequiredDescriptionDefault
urlNo
kindYes
fileIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already establish read-only, idempotent, non-destructive, closed-world behavior. The description adds useful context beyond them by specifying that the generated S3 URL is presigned and short-lived, expiring in about two minutes.

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?

It is one tightly written sentence with the key details front-loaded: short expiry, S3 URL, preview/download use, file type, and id source. There is no redundant wording.

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 a fully described single-parameter schema, an output schema, and safety annotations, the description covers everything needed to invoke the tool. The only meaningful gap is sibling differentiation against get_download_url.

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%, so the single fileId parameter is already fully documented. The description reinforces that the id comes from list_user_files but adds no format or validation detail beyond 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 description states a specific action and resource: retrieving a short-lived presigned S3 URL for a previously uploaded user file by id. It also ties the fileId source to list_user_files, but it does not explicitly distinguish this from the sibling get_download_url.

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?

It gives implied usage for previewing or downloading an uploaded CV/resume file and tells the caller where the file id comes from. It does not say when to prefer this over get_download_url or export_file, nor does it list exclusions.

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

All Coverlttr toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources