Skip to main content
Glama
mnoomnoo

resume-mcp-server

by mnoomnoo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

search_resumes_by_skill

Read-onlyIdempotent

Find resumes by matching one or more skills. Returns resume ID and matched skill names, with pagination support for browsing large results.

Instructions

Find which resumes list one or more given badge skills. Returns resume identity and matched skill names only — more token-efficient than list_resumes when filtering by skill. Accepts either a single skill string or a list of skills to filter by multiple at once.

Each result includes: id, first_name, last_name, matched_skills. Response includes total_count, items, has_more, next_offset, and message for pagination.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoToken match mode. For a single skill: 'and' (default) requires all words to appear in the skill title, 'or' requires any word to match, 'regex' treats it as a case-insensitive regular expression. For multiple skills, mode also controls whether a resume must match EACH skill in the list ('and') or ANY skill in the list ('or'); 'regex' mode combines multiple skills with OR semantics.and
limitNoMaximum number of results to return (default 100)
skillYesSkill title fragment, or list of fragments, to search for (case-insensitive, partial match)
offsetNoNumber of results to skip for pagination (default 0)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv1.0.7
    • addedInput schema / properties / limit
      Added value: +{
+  "default": 100,
+  "description": "Maximum number of results to return (default 100)",
+  "type": "integer"
+}
    • changedInput schema / properties / mode / description
      Previous value: -"Token match mode — 'and' (default) requires all words to appear in the skill title; 'or' requires any word to match"New value: +"Token match mode. For a single skill: 'and' (default) requires all words to appear in the\n  skill title, 'or' requires any word to match, 'regex' treats it as a case-insensitive\n  regular expression. For multiple skills, mode also controls whether a resume must match\n  EACH skill in the list ('and') or ANY skill in the list ('or'); 'regex' mode combines\n  multiple skills with OR semantics."
    • addedInput schema / properties / offset
      Added value: +{
+  "default": 0,
+  "description": "Number of results to skip for pagination (default 0)",
+  "type": "integer"
+}
    • addedInput schema / properties / skill / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  }
+]
    • changedInput schema / properties / skill / description
      Previous value: -"Skill title fragment to search for (case-insensitive, partial match)"New value: +"Skill title fragment, or list of fragments, to search for (case-insensitive, partial match)"
    • removedInput schema / properties / skill / type
      Removed value: -"string"
    • addedOutput schema / additionalProperties
      Added value: +true
    • removedOutput schema / properties
      Removed value: -{
-  "result": {
-    "items": {
-      "additionalProperties": true,
-      "type": "object"
-    },
-    "type": "array"
-  }
-}
    • removedOutput schema / required
      Removed value: -[
-  "result"
-]
    • removedOutput schema / x-fastmcp-wrap-result
      Removed value: -true
  2. Changed1 schema field changedv1.0.6
    • addedInput schema / properties / mode
      Added value: +{
+  "default": "and",
+  "description": "Token match mode — 'and' (default) requires all words to appear in the skill title; 'or' requires any word to match",
+  "type": "string"
+}
  3. First observedv1.0.1

TDQS

A4.7/5.0
Behavior5/5

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

The description adds valuable behavioral context beyond the readOnlyHint and idempotentHint annotations, such as returning only resume identity and matched skill names, and pagination details. No contradictions with annotations.

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?

The description is concise with three sentences, front-loading the purpose and usage, then listing output fields. Every sentence adds value with no redundancy.

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?

Given the existence of an output schema, the description provides sufficient context: purpose, input, output fields, and pagination. It covers the essential aspects for an agent to use the tool correctly.

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 baseline is 3. The description reinforces the skill parameter flexibility but does not add new meaning beyond the schema. The mention of result fields aids understanding but pertains to output, not parameter semantics.

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

Purpose5/5

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

The description clearly states the verb 'Find' and the resource 'resumes', specifying that it filters by badge skills. It explicitly distinguishes itself from the sibling tool 'list_resume_summaries' by highlighting token efficiency for skill-based filtering.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly advises when to use this tool ('more token-efficient than list_resumes when filtering by skill') and explains that it accepts both a single skill and a list of skills, providing clear guidance on alternative usage.

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