Skip to main content
Glama
anmolvarshney77

CV Email MCP Server

by anmolvarshney77
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

Server Quality Checklist

50%
Profile completionA complete profile improves this server's visibility in search results.

  • Latest release: v1.0.0

  • Disambiguation5/5

    Each tool has a clearly distinct purpose: parse_cv loads CV data, ask_cv queries it, and send_email sends a notification. There is no functional overlap between the three.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (parse_cv, ask_cv, send_email), using snake_case throughout. The naming is uniform and predictable.

    Tool Count5/5

    With only 3 tools, the server is tightly scoped to its stated purpose of CV parsing, querying, and email notification. This is well within the ideal range and each tool earns its place.

    Completeness4/5

    The tools cover the core workflow of parsing a CV, asking about its content, and sending an email. Minor gaps exist, such as no direct ability to update the parsed CV or manage email templates, but these are likely outside the server's narrow scope.

  • Average 3/5 across 3 of 3 tools scored.

    See the Tool Scores section below for per-tool breakdowns.

    • No community issues in the last 6 months
    • 0 commits in the last 12 weeks
    • No stable releases found
    • No critical vulnerability alerts
    • No high-severity vulnerability alerts
    • No code scanning findings
    • CI status not available

  • Add a LICENSE file by following GitHub's guide. Once GitHub recognizes the license, the system will automatically detect it within a few hours.

    If the license does not appear after some time, you can manually trigger a new scan using the MCP server admin interface.

    MCP servers without a LICENSE cannot be installed.

  • This repository includes a README.md file.

  • No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.

    Tip: use the "Try in Browser" feature on the server page to seed initial usage.

  • Add a glama.json file to provide metadata about your server.

  • If you are the author, simply .

    If the server belongs to an organization, first add glama.json to the root of your repository:

    {
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}

    Then . Browse examples.

  • Add related servers to improve discoverability.

How to sync the server with GitHub?

Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.

To manually sync the server, click the "Sync Server" button in the MCP server admin interface.

How is the quality score calculated?

The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).

Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.

Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).

Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.

Tool Scores

  • Behavior2/5

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

    With no annotations, the description must carry full behavioral disclosure. It states the primary action (send email) but does not disclose whether it actually sends or simulates, authentication requirements, rate limits, or any side effects.

    Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

    Conciseness3/5

    Is the description appropriately sized, front-loaded, and free of redundancy?

    The description is a single short sentence, which is concise, but it is also sparse and close to a tautology of the tool name. It doesn't add enough value to be considered well-structured, though it is not verbose.

    Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

    Completeness2/5

    Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

    For a side-effectful tool like sending email, the description is incomplete. It lacks any behavioral context, output expectations, or error handling information. The schema covers parameters but not usage context, and there is no output schema.

    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 description coverage is 100%, with each parameter having a clear description. The tool description adds no extra meaning beyond the schema, so the baseline of 3 applies.

    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 'Send an email notification' clearly states the action (send) and the resource (email). It is unambiguous and implicitly distinguishes from sibling tools (parse_cv, ask_cv) which deal with CV processing, but lacks specific scope like recipient or purpose.

    Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

    Usage Guidelines2/5

    Does the description explain when to use this tool, when not to, or what alternatives exist?

    No guidance is given on when to use this tool versus alternatives. The sibling tools are clearly different, but the description does not mention any context, exclusions, or alternative tools.

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

  • Behavior2/5

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

    With no annotations, the description carries full behavioral disclosure burden, but it only states 'Ask questions about your CV content.' It does not disclose what happens under the hood (e.g., whether it references a previously parsed CV, whether it has side effects, or what the response format is). This is minimal and leaves key behavior unspecified.

    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?

    The description is a single concise sentence, front-loaded with the core purpose. It has no redundancy or wasted words, but it is so brief that it misses essential context, slightly reducing the conciseness score.

    Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

    Completeness2/5

    Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

    For a tool with siblings and no annotations or output schema, the description is too incomplete. It does not explain how to use it in conjunction with parse_cv, what kind of answers it returns, or any prerequisites. The provided context signals (1 param, no output schema) indicate a simple tool, but the description still lacks necessary operational details.

    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?

    The schema covers 100% of the parameter descriptions (the 'question' param is described). The description adds little beyond the schema, so the baseline of 3 applies for high schema coverage.

    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 clearly states the tool's function: 'Ask questions about your CV content' with a specific verb ('ask') and resource ('CV content'). It distinguishes itself from siblings parse_cv (parsing) and send_email (sending) by focusing on interactive Q&A.

    Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

    Usage Guidelines2/5

    Does the description explain when to use this tool, when not to, or what alternatives exist?

    No guidance is provided on when to use this tool vs alternatives. It does not mention whether a CV must be parsed first, what types of questions are appropriate, or how it relates to parse_cv and send_email. The usage context is entirely implied.

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

  • Behavior2/5

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

    With no annotations provided, the description carries the full burden of behavioral disclosure, but it only offers a high-level action. It does not explain what 'load' means in practice, whether any state changes occur, error handling, supported PDF formats, or the return behavior. This is a significant gap for a tool that likely has side effects.

    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?

    The description is a single concise sentence, front-loaded with the verb and resource. There is no redundant information or fluff, making it efficiently structured for a tool description.

    Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

    Completeness2/5

    Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

    Given that there is no output schema and no annotations, the description should clarify what the tool returns or accomplishes. It only says 'Parse and load CV content' without explaining the outcome, the relationship to sibling tools, or any caveats. This leaves the agent under-informed about the tool's behavior and integration context.

    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?

    The schema already provides a complete description for the sole parameter (pdf_path: 'Path to the PDF file (optional, uses default if not provided)'), so the schema coverage is 100%. The tool description adds no extra semantic detail about the parameter beyond what the schema has, so a baseline score of 3 is appropriate.

    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 clearly states the action ('Parse and load') and the resource ('CV content from PDF file'), which distinguishes it from the sibling ask_cv tool. However, 'load' is somewhat vague—it does not specify whether the content is stored, returned, or made available for subsequent queries.

    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 usage guidance or alternatives are mentioned. The intended use is implied by the name 'parse_cv' (ingestion) versus sibling 'ask_cv' (querying), but the description does not state when to use this tool instead of the siblings or any prerequisites.

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

GitHub Badge

Glama performs regular codebase and documentation scans to:

  • Confirm that the MCP server is working as expected.
  • Confirm that there are no obvious security issues.
  • Evaluate tool definition quality.

Our badge communicates server capabilities, safety, and installation instructions.

Card Badge

MCP-Server-Resume-Parser MCP server

Copy to your README.md:

Score Badge

MCP-Server-Resume-Parser MCP server

Copy to your README.md:

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/anmolvarshney77/MCP-Server-Resume-Parser'

If you have feedback or need assistance with the MCP directory API, please join our Discord server