Skip to main content
Glama

CVder Shared Resumes

get_shared_resume

Fetch an owner-published CVder resume by its share link or slug.

    Accepts a full share URL (https://cvder.app/cv/rsm_...) or a bare
    rsm_ slug. Only resumes the owner has explicitly shared are
    reachable; email, phone and location are redacted by the server.

    format: "raw" (default) returns CVder's native resume shape;
    "json_resume" returns JSON Resume v1.0.0 (jsonresume.org) with
    CVder-only fields preserved under x_cvder — prefer it for
    interchange with other tools or when a standard schema matters.
    

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": {
      "share_link_or_slug": "<share_link_or_slug>"
    },
    "name": "get_shared_resume"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNoraw
share_link_or_slugYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and does substantial work: it discloses the access limitation (only owner-shared resumes are reachable), the server-side redaction of email, phone and location, and how the format parameter changes the payload including preservation of CVder-only fields under x_cvder. It stops short of describing failure behavior for expired, revoked, or malformed slugs, or any rate limiting, which keeps it off a 5.

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?

Three short paragraphs, front-loaded with purpose then constraints then parameter behavior; every sentence contributes. Slight redundancy in restating the rsm_ slug format twice and a minor formatting quirk with the indented block, but nothing that costs comprehension.

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?

An output schema exists, so return shape needn't be explained, and the remaining gaps are covered: scope, privacy/redaction, and format choice. The only meaningful omission for a network-fetch tool is what happens on a missing, private, or expired slug, leaving error handling to be discovered at call time.

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?

Schema description coverage is 0% — the properties carry only bare titles — so the description must compensate, and it does. It defines the accepted input grammar for share_link_or_slug ('https://cvder.app/cv/rsm_...' or a bare rsm_ slug) and names both legal values of format with their semantics and default, adding real meaning beyond the schema.

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 opens with a specific verb+resource ('Fetch an owner-published CVder resume') and names the identifier types (share link or slug), so the agent knows exactly what is retrieved and by what key. The scope qualifier 'owner-published' is stated immediately, leaving no ambiguity about which resumes are eligible.

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 clear conditional guidance for the format parameter: prefer 'json_resume' 'for interchange with other tools or when a standard schema matters', with 'raw' established as the default. It also states the reachability precondition (only explicitly shared resumes). There is no explicit when-not-to-use guidance or alternative-tool routing, but with no siblings exposed that omission is minor.

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