Skip to main content
Glama

Actual group – offres d'emploi

Find the most relevant Actual group agency

find_best_agency
Read-only

Recommend the Actual group agency, office, training centre or school best suited to a person's need, near a place in France. Covers employment agencies (intérim, CDD, CDI), Actual Talent offices (talent acquisition and assessment, mostly white-collar), Envergure centres (vocational training, skills assessment, career transition) and the group's schools (eSUP, Holberton…, often work-study). Ranks them by open offers for the given job, specialty (construction, logistics, medical, white-collar, school domain…) and distance. Returns address, phone, opening status and why each agency was picked. Pass the returned agency code to search_offers (agencyCode) to list that agency's offers.

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": {
      "location": "<location>"
    },
    "name": "find_best_agency"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobNoJob or field the person is looking for or hiring for, e.g. "électricien", "cariste", "aide-soignant".
limitNoNumber of agencies to return, 1 to 5. Defaults to 3.
purposeNofind_job: a candidate looking for work (default). hire: a company looking to recruit. assessment: a company wanting candidates or staff assessed (Actual Talent). training: vocational training, skills assessment or career change (Envergure). school: a degree or work-study programme (group schools). insertion: return-to-work support.
locationYesFrench town or postal code, e.g. "Le Mans" or "72000".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedInput schema / properties / context
      Removed value: -{
      -  "description": "Why are you calling this tool? Describe the job seeker's or recruiter's goal in one short sentence. Do not include names, emails or phone numbers.",
      -  "type": "string"
      -}
    • removedInput schema / properties / conversation_id
      Removed value: -{
      -  "description": "Pass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request.",
      -  "type": "string"
      -}
    • removedInput schema / properties / llm_model
      Removed value: -{
      -  "description": "The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. \"claude-opus-4-8\", \"gpt-5.2\"). Used for analytics only. If you do not know your model identifier with certainty, pass \"unknown\" — never guess.",
      -  "type": "string"
      -}
    • changedInput schema / required
      Previous value: -[
      -  "location",
      -  "context",
      -  "llm_model"
      -]New value: +[
      +  "location"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / context / description
      Previous value: -"Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\""New value: +"Why are you calling this tool? Describe the job seeker's or recruiter's goal in one short sentence. Do not include names, emails or phone numbers."
  3. Changed4 schema fields changed
    • addedInput schema / properties / context
      Added value: +{
      +  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
      +  "type": "string"
      +}
    • addedInput schema / properties / conversation_id
      Added value: +{
      +  "description": "Pass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request.",
      +  "type": "string"
      +}
    • addedInput schema / properties / llm_model
      Added value: +{
      +  "description": "The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. \"claude-opus-4-8\", \"gpt-5.2\"). Used for analytics only. If you do not know your model identifier with certainty, pass \"unknown\" — never guess.",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "location"
      -]New value: +[
      +  "location",
      +  "context",
      +  "llm_model"
      +]
  4. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is known. The description adds real behavioural value beyond that: ranking factors (open offers for the job, specialty, distance), the returned fields (address, phone, opening status, selection rationale), and the handoff to search_offers. It says nothing about result stability or rate limits, but that is minor for a read-only recommendation call.

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?

The core action and scope come first, then the coverage enumeration, then ranking, then the follow-up call — a sensible front-loaded order. The middle sentence listing agency categories is dense but each clause carries selection-relevant information; nothing is filler.

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?

There is no output schema, and the description fills that gap by naming what comes back (address, phone, opening status, and why each agency was picked). Combined with the ranking logic and the pointer to search_offers, an agent has everything needed to call this correctly for a 4-parameter, read-only tool.

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

Parameters4/5

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

Schema coverage is 100%, so parameter documentation already exists at baseline 3. The description goes further by mapping domain vocabulary onto the purpose semantics (intérim/CDD/CDI vs. white-collar talent vs. vocational training vs. work-study schools), which helps the agent pick a purpose value and a specialty string, and by explaining that the output agency code is the input to search_offers.

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?

Specific verb ("Recommend") plus resource ("Actual group agency, office, training centre or school") and a stated scope ("near a place in France"). It enumerates the sub-types covered (intérim agencies, Actual Talent, Envergure, schools) and names the downstream tool, so an agent can tell what this returns without opening the schema.

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

Usage Guidelines4/5

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

Clear context for use: match a person's need (job, specialty) to a nearby agency, then pass the returned agency code to search_offers. Explicit routing to search_offers is strong guidance. However, the sibling find_agencies is never mentioned, so the agent gets no rule for choosing between the two finders.

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.

Resources