Skip to main content
Glama
Sign In
MCP Resume & Email Assistant

MCP Resume & Email Assistant

by ThambimuthuAnush24
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Parse Resume

parseResume

Parses resume text or base64 PDF to extract structured information for further processing.

Instructions

Parse a resume file to extract information

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": {
      "resumeText": "<resumeText>"
    },
    "name": "parseResume"
  }
}

Input Schema

NameRequiredDescriptionDefault
resumeTextYesThe text content of the resume or a base64 encoded PDF

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations exist, so the description carries full burden. It fails to disclose behavior on malformed input, output format, error handling, or required permissions. Minimal information provided.

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, clear sentence. It is appropriately concise for a simple tool, though it could be slightly expanded without losing focus.

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 no output schema, the description should clarify what 'extract information' returns (e.g., structured data). It fails to cover return values, error cases, or the full context of operation.

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%, and the schema already describes 'resumeText' as text or base64 PDF. The description adds no additional meaning beyond the schema, meeting baseline but not exceeding.

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 tool's action ('Parse a resume file') and purpose ('extract information'). It is specific enough to distinguish from 'sendEmail', though it doesn't explicitly contrast with 'queryResume'.

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 on when to use this tool versus alternatives like 'queryResume'. No prerequisites, contexts, or exclusions are mentioned.

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