Skip to main content
Glama

mcp-knowledge

by io.github.getgapup

recruiting_architect

Read-only

Architecte du recrutement — Gapup agent-payable C-suite expertise (CHRO). Returns a structured, audited deliverable. Reference case: Stripe France — 12 postes Q3 2026 · sourcing multi-canaux + employer brand + frameworks d'entretien + parcours candidat · time-to-hire -45%. Inputs are validated server-side — send the documented case fields.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
asyncNoIf true, returns a job_id immediately (<200ms) instead of waiting for the result. Poll the result with job_result(job_id). Use for slow tools to avoid client timeouts.
focusNo
rolesYes
budgetYes
companyYes
preferencesYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed11 schema fields changed
    • addedInput schema / properties / budget / properties
      Added value: +{
+  "averageSalaryRangeEur": {
+    "properties": {
+      "max": {
+        "type": "number"
+      },
+      "min": {
+        "type": "number"
+      }
+    },
+    "required": [
+      "min",
+      "max"
+    ],
+    "type": "object"
+  },
+  "totalRecruitmentBudgetEur": {
+    "minimum": 0,
+    "type": "number"
+  }
+}
    • addedInput schema / properties / budget / required
      Added value: +[
+  "totalRecruitmentBudgetEur",
+  "averageSalaryRangeEur"
+]
    • addedInput schema / properties / company / properties
      Added value: +{
+  "employerBrandStrength": {
+    "enum": [
+      "unknown",
+      "emerging",
+      "good",
+      "strong"
+    ],
+    "type": "string"
+  },
+  "fte": {
+    "minimum": 1,
+    "type": "integer"
+  },
+  "fundingStage": {
+    "maxLength": 80,
+    "type": "string"
+  },
+  "location": {
+    "maxLength": 120,
+    "minLength": 2,
+    "type": "string"
+  },
+  "name": {
+    "maxLength": 120,
+    "minLength": 2,
+    "type": "string"
+  },
+  "sector": {
+    "maxLength": 120,
+    "minLength": 2,
+    "type": "string"
+  }
+}
    • addedInput schema / properties / company / required
      Added value: +[
+  "name",
+  "sector",
+  "fte",
+  "location",
+  "employerBrandStrength"
+]
    • addedInput schema / properties / focus / maxLength
      Added value: +400
    • addedInput schema / properties / preferences / properties
      Added value: +{
+  "diversityFocusAreas": {
+    "items": {
+      "type": "string"
+    },
+    "maxItems": 6,
+    "type": "array"
+  },
+  "geography": {
+    "items": {
+      "type": "string"
+    },
+    "maxItems": 8,
+    "minItems": 1,
+    "type": "array"
+  },
+  "remotePreference": {
+    "enum": [
+      "full-remote",
+      "hybrid",
+      "office-first",
+      "office-only"
+    ],
+    "type": "string"
+  }
+}
    • addedInput schema / properties / preferences / required
      Added value: +[
+  "geography",
+  "remotePreference"
+]
    • addedInput schema / properties / roles / items
      Added value: +{
+  "properties": {
+    "department": {
+      "maxLength": 80,
+      "minLength": 2,
+      "type": "string"
+    },
+    "keyMissionPoints": {
+      "maxLength": 400,
+      "type": "string"
+    },
+    "roleId": {
+      "maxLength": 80,
+      "minLength": 2,
+      "type": "string"
+    },
+    "roleTitle": {
+      "maxLength": 120,
+      "minLength": 2,
+      "type": "string"
+    },
+    "roleType": {
+      "enum": [
+        "engineering",
+        "product",
+        "design",
+        "data",
+        "sales",
+        "customer-success",
+        "marketing",
+        "people-ops",
+        "finance",
+        "operations",
+        "legal",
+        "executive",
+        "other"
+      ],
+      "type": "string"
+    },
+    "seniority": {
+      "enum": [
+        "junior",
+        "mid",
+        "senior",
+        "staff",
+        "principal",
+        "manager",
+        "director",
+        "vp",
+        "c-level"
+      ],
+      "type": "string"
+    },
+    "targetStartDate": {
+      "type": "string"
+    },
+    "teamSizeReporting": {
+      "minimum": 0,
+      "type": "integer"
+    }
+  },
+  "required": [
+    "roleId",
+    "roleTitle",
+    "roleType",
+    "seniority",
+    "department",
+    "targetStartDate"
+  ],
+  "type": "object"
+}
    • addedInput schema / properties / roles / maxItems
      Added value: +15
    • addedInput schema / properties / roles / minItems
      Added value: +1
    • addedInput schema / required
      Added value: +[
+  "company",
+  "roles",
+  "budget",
+  "preferences"
+]
  2. First observed

TDQS

C2.6/5.0
Behavior3/5

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

The description adds behavioral context beyond annotations (readOnlyHint, openWorldHint) by noting server-side input validation and the nature of the deliverable. However, it does not discuss other important behaviors like async handling or what 'open world' entails, leaving gaps.

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

Conciseness3/5

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

The description is a single paragraph that is moderately concise but includes an extraneous case study (Stripe France) that may not be relevant for all uses. Sentence order is acceptable but could be more streamlined.

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?

Given the tool's complexity (multiple nested objects, no output schema, low schema coverage), the description is insufficient. It omits details on output format, return values, and how to handle the async option, leaving the agent with significant gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 17%, and the tool description does little to explain parameters. It merely says 'send the documented case fields' without detailing the six properties, their required status, or their roles. The async parameter is described in schema but not in the main description.

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

Purpose3/5

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

The description states it is an 'Architecte du recrutement' that 'returns a structured, audited deliverable,' giving a general sense of purpose through a recruitment architecture case. However, it lacks a clear, generic verb-resource statement and does not distinguish itself from sibling tools like talent_intelligence or job_postings_intelligence.

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?

No explicit guidance on when to use this tool versus alternatives. The instruction 'send the documented case fields' is too vague and does not clarify context, prerequisites, or exclusions.

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

All mcp-knowledge toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

C2.8/5.0
Disambiguation2/5

Many tools have overlapping purposes, especially in competitive intelligence, ESG, and risk assessment. For example, there are multiple tools for competitor analysis (competitive_deep_dive, competitor_intel, competitor_moves, etc.) with unclear boundaries. Agents would struggle to select the correct tool without deep understanding of subtle differences.

Naming Consistency2/5

Tool names are a mix of English and French, and follow no consistent pattern. Some use snake_case (e.g., abm_architect, action_plan_esg), while others are verb-focused (e.g., content_catalog, fx_rate). The lack of a uniform naming convention makes it hard for agents to predict tool names.

Tool Count1/5

With 271 tools, the server is excessively large. Even for a broad knowledge domain, this number of tools makes discovery and selection inefficient. Typical coherent servers have 3-15 tools; this has an order of magnitude more, indicating poor scoping.

Completeness3/5

The tool set covers many domains (compliance, finance, marketing, HR, etc.), but the coverage is uneven due to redundancy. Key areas have multiple overlapping tools, while some sub-domains may still have gaps. Overall, the surface is broad but not well-curated.

Resources