Skip to main content
Glama
KaungHtunThant

j-hunt-mcp

set_resume

Store or replace your resume text to be used by job tailoring prompts.

Instructions

Store/replace the resume text used by the tailoring prompts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
resume_textYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
full_nameNo
headlineNo
skillsNo
years_experienceNo
locations_preferredNo
remote_okNo
resume_textNo
linksNo
Behavior2/5

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

No annotations provided, and the description only indicates mutation (store/replace) without detailing side effects, size limits, or overwrite behavior.

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 with no wasted words, but it is too brief to provide necessary context for an AI agent.

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 the tool has an output schema and one required parameter, the description lacks details on return values or error conditions, leaving the agent underinformed for a simple but critical operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, and the description does not add meaning to the single parameter 'resume_text'. No format, length, or semantics beyond what the parameter name suggests.

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 (store/replace) and the resource (resume text). It is specific and distinct from sibling tools like get_profile or update_profile.

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 vs alternatives like update_profile. No mention of prerequisites or conditions for usage.

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

Install Server

Other Tools

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/KaungHtunThant/j-hunt-mcp'

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