Skip to main content
Glama

Rechercher des collaborateurs

rechercher_collaborateurs

Search available consultants by skill, agency, and month, with optional minimum level and days. Get a short list sorted by skill level and availability.

Instructions

Recherche des collaborateurs disponibles selon une competence, une agence et un mois. Retourne une liste courte, triee par niveau de competence puis par disponibilite.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "rechercher_collaborateurs"
  }
}

Input Schema

NameRequiredDescriptionDefault
moisNoMois de besoin au format AAAA-MM (ex. '2026-11')
agenceNoRestreindre a une agence
limiteNoNombre maximum de resultats
jours_minNoNombre minimum de jours disponibles sur le mois demande
competenceNoCompetence recherchee, en minuscules (ex. 'react', 'kafka', 'kubernetes')
niveau_minNoNiveau minimum sur cette competence, de 1 a 5

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose two useful traits beyond the schema: results are a short list and are sorted by skill level then availability. However, it says nothing about authentication requirements, rate limits, empty-result behavior, or what constitutes 'disponible', which are relevant for a staffing search.

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?

Two sentences, both earning their place: the first states purpose and filter axes, the second states the return shape and ordering. Front-loaded and free of redundancy.

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

Completeness3/5

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

With six parameters, no required fields, and no output schema, the description should say more about what the returned collaborator entries contain and how vacancy/jours_min interact. It covers the ranking rule and result size but leaves the returned fields and matching semantics unspecified.

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%, with each of the six parameters documented (format for mois, enum values for agence, bounds for limite, jours_min, niveau_min, lowercase convention for competence). The description only names three of the six filter axes and adds no syntax or format detail beyond the schema, so baseline 3 applies.

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 (Recherche) and resource (collaborateurs) plus the three filter axes (competence, agence, mois), so the agent knows exactly what it returns. It does not, however, explicitly differentiate itself from siblings like obtenir_collaborateur or analyser_staffing_mission, which an agent must infer.

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 verb 'recherche' and the filter parameters, so an agent can guess this is the discovery step before reserver_collaborateur. There is no explicit when-to-use statement, no mention of when to prefer obtenir_collaborateur for a single known person, and no exclusions.

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