Skip to main content
Glama

Jobiba Jobs: Job Search, Salary, CV & Apply

Score my match

job_match_score
Read-onlyIdempotent

Scores the signed-in candidate's profile against an active Jobiba job using only profile and job facts, returning an indicative score, evidence confidence, matched skills, missing evidence and next actions. It is not a hiring prediction.

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": {
      "jobId": "<jobId>"
    },
    "name": "job_match_score"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYes

Output Schema

NameRequiredDescriptionDefault
scoreYes
breakdownYes
confidenceYes
nextActionsYes
matchedSkillsYes
missingSkillsYes
scoredDimensionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare this as read-only, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds two genuine pieces of context: results derive only from profile and job facts, and the output is explicitly framed as non-predictive. However, the list of returned fields duplicates what the existing output schema already documents, so the net addition is modest.

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?

Two sentences, front-loaded with the core action, with the scope constraint immediately following. The enumeration of return fields is somewhat redundant given the output schema and could be trimmed without loss.

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 one-parameter read-only tool with a full output schema and rich annotations, the description covers action, data basis and interpretation caveat. Remaining gaps are minor: no statement of what happens for an inactive or unknown job, and no note on authentication beyond 'signed-in candidate'.

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?

With a single parameter at 0% schema description coverage, the description must carry the load. Saying 'an active Jobiba job' conveys that jobId must reference a currently active posting, which is useful semantics beyond the bare string type, but it never names the parameter or states format or failure behavior for an invalid or closed job.

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: it scores the signed-in candidate's profile against an active job. Scope qualifiers ('active' job, 'only profile and job facts') narrow it meaningfully, though no sibling such as profile_strength or application_readiness is named to sharpen the distinction.

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 implied by the phrase 'against an active Jobiba job' rather than stated as a when-to-use rule. There is no guidance on when to pick this over profile_strength or application_readiness, and no explanation of what happens when the job is not active. The 'not a hiring prediction' caveat is a framing note, not a selection rule.

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.