Skip to main content
Glama

business_resume_job_match

Read-onlyIdempotent

Resume and job post keyword match

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": "<resume>",
      "jobPost": "<jobPost>"
    },
    "name": "business_resume_job_match"
  }
}

Input Schema

NameRequiredDescriptionDefault
resumeYesThe resume as plain text (up to 100,000 characters).
jobPostYesThe job posting as plain text (up to 100,000 characters). Paste the whole posting: the keywords come from how often it repeats words and two-word phrases.
maxKeywordsNoHow many posting keywords to check, 1 to 100. Default 40.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Added

TDQS

C2.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. Beyond that the description adds nothing: it does not say whether the result is a score, a keyword list, or matched/missing terms, nor how the matching is performed, despite there being no output schema to fall back on.

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

Conciseness2/5

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

It is short, but the brevity reflects under-specification rather than disciplined concision: a single fragment with no verb, no object of the result, and nothing front-loaded that an agent can act on. There is no wasted word, but also almost no 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?

For a three-parameter analytical tool with no output schema, the description should at minimum convey what the match produces (per-keyword hits, coverage percentage, missing keywords) and how keywords are derived. None of that is present, leaving a significant gap for an agent deciding whether this answers a 'how well does my resume fit this job' question.

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%, and the schema itself explains the resume/jobPost text limits and the maxKeywords range with a default. The description contributes no additional meaning about parameters, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a bare noun phrase, 'Resume and job post keyword match', that essentially restates the tool name (business_resume_job_match) plus the word 'keyword'. It never states the operation (compare? score? extract? rank?) or what the agent gets back, so it is close to tautological rather than a specific verb+resource statement.

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?

There is no when-to-use guidance, no mention of when not to use it, and no routing to related tools such as business_resume_outline or business_blind_cv that an agent might reasonably confuse with a resume-analysis task. The agent must infer the use case entirely from the name.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources