Skip to main content
Glama
Sign In
Placed MCP Server

Placed MCP Server

by Exidian-Tech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

optimize_resume_section

Optimize a resume section for a target job description by analyzing and improving the content of experience, skills, or summary.

Instructions

Optimize a specific resume section (experience, skills, summary) using AI.

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>",
      "section_type": "<section_type>",
      "section_data": "<section_data>"
    },
    "name": "optimize_resume_section"
  }
}

Input Schema

NameRequiredDescriptionDefault
resume_idYesResume ID to optimize
section_typeYesSection to optimize
section_dataYesCurrent section content
job_descriptionNoTarget job description for optimization

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations exist, so the description must disclose behavior. It only mentions 'using AI' without explaining side effects (e.g., whether it saves changes), required permissions, or any destructive actions. This is insufficient for a tool that likely modifies a resume.

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 sentence, which is concise but lacks structure. It does not use bullet points or clear sections, making it harder to scan for key information.

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?

With 4 parameters, no output schema, and many sibling tools, the description is too minimal. It fails to explain what 'optimize' entails, what the tool returns, or how it interacts with other resume functions. A more comprehensive description is needed.

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 parameter descriptions. The tool description adds little meaning beyond the schema, just stating the section types. It does not explain how optional parameters like 'job_description' affect the optimization.

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 verb 'optimize' and the resource 'resume section', listing example sections. However, it does not differentiate from similar sibling tools like 'optimize_resume_for_job' or 'improve_bullet_point', which also involve optimization.

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 versus alternatives such as 'optimize_resume_for_job' or 'improve_bullet_point'. There is no indication of prerequisites or context.

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