Skip to main content
Glama
Sign In

CareerHolo

by io.github.amisini
OverviewDiscussionsAdmin

Jobs that fit my skills

match_my_skills
Read-onlyIdempotent

Rank open tech jobs by how well they fit a person's skills, the way CareerHolo's resume match does: a match percentage for each job, the skills they have and miss, and which skill to learn next for more jobs. Send skills only - never a name, email or the resume's text. Nothing is stored.

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": {
      "skills": "<skills>"
    },
    "name": "match_my_skills"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoA city in that country, e.g. "Berlin"
levelNoThe person's level
rolesNoKinds of job wanted; jobs next to them count too
skillsYesThe person's skills, e.g. ["Python", "Django", "PostgreSQL", "AWS"]
countryNoWhere the person works from, e.g. "Germany": jobs there and remote jobs open to it
work_typeNoOnly this way of working
visa_sponsorshipNoOnly jobs that sponsor a visa

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavior: what the response contains and the assurance that "Nothing is stored," plus a privacy constraint against sending names, emails, or resume text. It stops short of describing result limits or ranking stability.

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 ranking purpose and then the privacy constraint, with no filler. The "the way CareerHolo's resume match does" clause is slightly promotional but does convey the output shape efficiently.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With seven parameters, no output schema, and a privacy-sensitive input, the description carries the right load: it explains the ranking result structure that would otherwise be missing, and states the PII exclusion clearly. An agent can call it correctly from this plus the fully documented schema.

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%, so every parameter including city, country, roles, level, work_type and visa_sponsorship is already documented in the schema. The description adds only a framing hint that skills are the sole identity input, and does not clarify the interaction between city and country or how roles adjacency is applied.

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?

States a specific verb and resource: "Rank open tech jobs by how well they fit a person's skills," and previews the ranked output (match percentage, skills had/missed, next skill to learn). That is clearly distinct from a plain search like search_jobs or company_jobs, though it never names an alternative to route against.

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 framing (use it when you want skill-fit ranking rather than a plain listing), but there is no explicit when-to-use, when-not-to-use, or named alternative such as search_jobs. The "Send skills only" sentence is a data-handling constraint, not selection guidance.

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

All CareerHolo toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources