Skip to main content
Glama

Match focus areas to a role and motivation

match_mentoring_focus
Read-onlyIdempotent

Resolves role_band + motivation through the same routing the website uses and returns suggested focus areas plus the recommended package with real prices. Map free-text answers to the closest valid id; on bad input the error lists the valid ids — re-ask rather than guessing. Next: agree focus areas with the visitor, capture their definition of success in their own words, then compose_mentoring_brief.

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": "match_mentoring_focus"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextNoOptional. A short description of your goal and why you are calling this tool. Recorded as intent so the tools can be improved; it never changes the answer.
audienceNoPass the audience answer — it changes the recommendation. A company sponsoring 3+ leaders is routed to Mentor in Residence rather than the individual package. One of: individual, company.
role_bandNoRequired. One of the role ids listed in the get_mentoring_options briefing
motivationNoRequired. One of the motivation ids listed in the get_mentoring_options briefing
leaders_countNoCompany deals: how many leaders are being sponsored. Required for the company recommendation to be correct.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / motivation / description
      Previous value: -"Required. One of the motivation ids from get_mentoring_options question_2"New value: +"Required. One of the motivation ids listed in the get_mentoring_options briefing"
    • changedInput schema / properties / role_band / description
      Previous value: -"Required. One of the role ids from get_mentoring_options question_1"New value: +"Required. One of the role ids listed in the get_mentoring_options briefing"
  2. Changed10 schema fields changed
    • changedInput schema / properties / audience / description
      Previous value: -"Pass the audience answer — it changes the recommendation. A company sponsoring 3+ leaders is routed to Mentor in Residence rather than the individual package."New value: +"Pass the audience answer — it changes the recommendation. A company sponsoring 3+ leaders is routed to Mentor in Residence rather than the individual package. One of: individual, company."
    • removedInput schema / properties / audience / enum
      Removed value: -[
      -  "individual",
      -  "company"
      -]
    • changedInput schema / properties / context / description
      Previous value: -"Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): \"Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization.\""New value: +"Optional. A short description of your goal and why you are calling this tool. Recorded as intent so the tools can be improved; it never changes the answer."
    • addedInput schema / properties / leaders_count / anyOf
      Added value: +[
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "string"
      +  }
      +]
    • removedInput schema / properties / leaders_count / maximum
      Removed value: -9007199254740991
    • removedInput schema / properties / leaders_count / minimum
      Removed value: --9007199254740991
    • removedInput schema / properties / leaders_count / type
      Removed value: -"integer"
    • changedInput schema / properties / motivation / description
      Previous value: -"One of the motivation ids from get_mentoring_options question_2"New value: +"Required. One of the motivation ids from get_mentoring_options question_2"
    • changedInput schema / properties / role_band / description
      Previous value: -"One of the role ids from get_mentoring_options question_1"New value: +"Required. One of the role ids from get_mentoring_options question_1"
    • removedInput schema / required
      Removed value: -[
      -  "role_band",
      -  "motivation",
      -  "context"
      -]
  3. Changed2 schema fields changed
    • addedInput schema / properties / context
      Added value: +{
      +  "description": "Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): \"Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization.\"",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "role_band",
      -  "motivation"
      -]New value: +[
      +  "role_band",
      +  "motivation",
      +  "context"
      +]
  4. Changed2 schema fields changed
    • addedInput schema / properties / audience
      Added value: +{
      +  "description": "Pass the audience answer — it changes the recommendation. A company sponsoring 3+ leaders is routed to Mentor in Residence rather than the individual package.",
      +  "enum": [
      +    "individual",
      +    "company"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / leaders_count
      Added value: +{
      +  "description": "Company deals: how many leaders are being sponsored. Required for the company recommendation to be correct.",
      +  "maximum": 9007199254740991,
      +  "minimum": -9007199254740991,
      +  "type": "integer"
      +}
  5. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely new behavior: results mirror the website's routing, prices returned are real, and invalid input produces an error enumerating valid ids. It stops short of describing the shape of the returned focus areas or package, but that is a minor gap for a read-only lookup.

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?

Three tight sentences, front-loaded with what the tool does, followed by input-handling rules and the next step. No filler or restatement of the name.

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 no output schema, the description still explains what comes back (suggested focus areas and a recommended package with real prices). Combined with the error-handling note and the explicit next step, an agent has everything needed to call it and act on the result.

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 the baseline is 3, but the description adds meaning beyond the schema: role_band and motivation are ids sourced from the get_mentoring_options briefing and free-text answers must be mapped to the closest valid id. It also reinforces that audience changes the recommendation, which the schema states but the description frames as a routing rule.

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?

States a specific verb and resource: resolves role_band + motivation via the same routing the website uses, returning suggested focus areas plus a recommended package with real prices. This is clearly distinguishable from get_mentoring_options (which supplies the ids) and compose_mentoring_brief (the named next step).

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?

Gives explicit operational guidance: map free-text answers to the closest valid id, and on bad input re-ask rather than guess because the error lists valid ids. It also names the downstream sequence (agree focus areas, capture the visitor's definition of success, then compose_mentoring_brief), so the agent knows both how to call it and what to do next.

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