Skip to main content
Glama
Sign In
cv-mirror-mcp

cv-mirror-mcp

by goofypluto999
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_express_url

Retrieve a URL to open the CV Mirror web tool for drag-and-drop, side-by-side parser view of a CV.

Instructions

Returns the URL for the visual web companion tool (CV Mirror) where the user can drag-drop a CV and see the side-by-side parser view in their browser. Useful when the user wants the visual reading-order overlay or doesn't want to share a file path.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_express_url"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/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. States it returns a URL, implying read-only, but does not explicitly declare non-destructive behavior or other constraints.

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?

Two sentences, no unnecessary words, front-loaded with purpose. Highly efficient.

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?

Adequate for a zero-parameter, no-output-schema tool. Explains function and usage context. Minor gap: doesn't explicitly state no input needed, but schema implies it.

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?

No parameters (schema coverage 100%), baseline 4. Description adds meaning by explaining the purpose of the URL beyond the empty 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?

Clear verb+resource: 'Returns the URL' for a specific visual tool (CV Mirror). Distinguishes from siblings (analyze_cv, lint_for_vendor) by offering a different capability.

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?

States when it's useful (visual reading-order overlay, avoiding file path sharing). Does not explicitly exclude alternative uses but context is clear.

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