Skip to main content
Glama
Sign In
Placed MCP Server

Placed MCP Server

by Exidian-Tech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_resume_pdf_url

Obtain a temporary download URL for a resume PDF. Provide the resume ID to get a link that expires in 15 minutes.

Instructions

Get a temporary download URL for a resume PDF (expires in 15 minutes)

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": {
      "resume_id": "<resume_id>"
    },
    "name": "get_resume_pdf_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
resume_idYesResume ID to download

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. It discloses the temporary nature (15-min expiry) which is key. However, it lacks other behavioral traits like side effects, rate limits, or whether it modifies state. For a read-like operation, basic info is given but incomplete.

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?

Single sentence directly conveys the purpose and key characteristic (expiry). No filler, every word adds value. Perfectly concise for such a simple tool.

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?

Given one parameter and no output schema, the description is fairly complete: it states what the tool does and the return type (temporary URL). It doesn't specify the URL format or any error conditions, but for a straightforward retrieval tool, it suffices. Minor gap: no mention of the return structure.

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% with description 'Resume ID to download'. The tool description adds no extra meaning beyond the schema, as it merely restates that the parameter identifies the resume. With high schema coverage, this is the baseline.

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?

Description clearly states the action (get), the resource (resume PDF), and key property (temporary URL, expires in 15 min). It distinguishes from sibling tools like get_resume_docx_url (DOCX) and get_resume (data) through the PDF and temporary URL specificity.

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?

No explicit when-to-use or when-not-to-use guidance. The description implies usage for downloading a resume PDF via a URL, but does not mention alternatives (e.g., get_resume_docx_url for DOCX) or context (e.g., required authentication). Usage context is implicit but not elaborated.

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

Deploy Server

Other Tools