Skip to main content
Glama
Sign In
career-mcp

career-mcp

by sindhujaIBM
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

save_jd

Store a job description for a company and role, create an application record, and mark it as the active application using either pasted text or a file path.

Instructions

Store a job description for a company/role and mark it as the active application. Creates a new application record. Provide exactly one of jd_text or jd_path.

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": {
      "company": "<company>",
      "role": "<role>"
    },
    "name": "save_jd"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleYes
companyYes
jd_pathNoAbsolute path to a .pdf, .txt, or .md job description file to read instead of passing raw text
jd_textNoThe full job description text

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the key side effect (creates an application record and makes it active), but it says nothing about what happens to a previously active application, whether re-saving the same company/role overwrites or duplicates, required preconditions, or what the call returns.

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?

Three short sentences, front-loaded with the core action and side effect, with the parameter constraint last. Nothing is redundant or padded.

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?

For a 4-parameter mutation tool with no annotations and no output schema, the definition covers the action, the record creation, and the input exclusivity rule. Remaining gaps (overwrite semantics for an existing active application, return value) are real but narrow.

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 only 50% of parameters, and the description compensates partially by stating "Provide exactly one of jd_text or jd_path" — a mutual-exclusivity rule the schema does not encode (there is no oneOf). However, company and role remain undocumented beyond the terse "for a company/role" phrasing, so half the surface is still unexplained.

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 gives a specific verb and resource ("Store a job description for a company/role") plus the downstream effect ("mark it as the active application. Creates a new application record"). An agent can distinguish it from save_resume or save_story by the object being stored, though no sibling is named explicitly.

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?

Usage is only implied: the phrase "mark it as the active application" hints this is the step taken when starting to apply to a role, but there is no explicit when-to-use/when-not, no statement of prerequisites, and no comparison to alternatives such as save_output or list_applications.

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