Skip to main content
Glama

Compose the mentoring brief: the artifact + the authoritative price

compose_mentoring_brief
Read-onlyIdempotent

The accumulator — call after every change. Echoes the brief as a briefing (audience, role, motivation, focus areas, definition of success, chosen package) with the authoritative catalog price and the AI-channel figure (never do the arithmetic yourself). For company deals it states whether the free-sessions concession applies. Read the brief back to the visitor; when they explicitly agree on the price, call send_mentoring_offer with price_agreed true.

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

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.
audienceNoRequired. One of: individual, company.
offer_idNoRequired. One of: single-session, first-quarter, monthly, mentor-in-residence, mentor-in-residence-2day.
role_bandNoRequired.
motivationNoRequired.
visibilityNoVisibility answer id from get_mentoring_options topic: visibility (consent capture — 'private' is a first-class answer)
leaders_countNoCompany deals: how many leaders are being sponsored
focus_area_idsNoRequired. Agreed focus area ids (visitor can pick any from the taxonomy)
company_contextNoCompany deals: company name + anything relevant
success_definitionNoRequired. The visitor's definition of success, in their own words

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / visibility / description
      Previous value: -"Visibility answer id from get_mentoring_options visibility_question (consent capture — 'private' is a first-class answer)"New value: +"Visibility answer id from get_mentoring_options topic: visibility (consent capture — 'private' is a first-class answer)"
  2. Changed1 schema field changed
    • changedInput schema / properties / offer_id / description
      Previous value: -"Required. One of: single-session, first-quarter, two-quarters, monthly, mentor-in-residence."New value: +"Required. One of: single-session, first-quarter, monthly, mentor-in-residence, mentor-in-residence-2day."
  3. Changed17 schema fields changed
    • addedInput schema / properties / audience / description
      Added value: +"Required. 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 / focus_area_ids / anyOf
      Added value: +[
      +  {
      +    "items": {
      +      "type": "string"
      +    },
      +    "type": "array"
      +  },
      +  {
      +    "type": "string"
      +  }
      +]
    • changedInput schema / properties / focus_area_ids / description
      Previous value: -"Agreed focus area ids (visitor can pick any from the taxonomy)"New value: +"Required. Agreed focus area ids (visitor can pick any from the taxonomy)"
    • removedInput schema / properties / focus_area_ids / items
      Removed value: -{
      -  "type": "string"
      -}
    • removedInput schema / properties / focus_area_ids / type
      Removed value: -"array"
    • 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"
    • addedInput schema / properties / motivation / description
      Added value: +"Required."
    • addedInput schema / properties / offer_id / description
      Added value: +"Required. One of: single-session, first-quarter, two-quarters, monthly, mentor-in-residence."
    • removedInput schema / properties / offer_id / enum
      Removed value: -[
      -  "single-session",
      -  "first-quarter",
      -  "two-quarters",
      -  "monthly",
      -  "mentor-in-residence"
      -]
    • addedInput schema / properties / role_band / description
      Added value: +"Required."
    • changedInput schema / properties / success_definition / description
      Previous value: -"The visitor's definition of success, in their own words"New value: +"Required. The visitor's definition of success, in their own words"
    • removedInput schema / required
      Removed value: -[
      -  "audience",
      -  "role_band",
      -  "motivation",
      -  "focus_area_ids",
      -  "success_definition",
      -  "offer_id",
      -  "context"
      -]
  4. Changed1 schema field changed
    • changedInput schema / properties / offer_id / enum
      Previous value: -[
      -  "single-session",
      -  "first-quarter",
      -  "monthly",
      -  "mentor-in-residence"
      -]New value: +[
      +  "single-session",
      +  "first-quarter",
      +  "two-quarters",
      +  "monthly",
      +  "mentor-in-residence"
      +]
  5. 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: -[
      -  "audience",
      -  "role_band",
      -  "motivation",
      -  "focus_area_ids",
      -  "success_definition",
      -  "offer_id"
      -]New value: +[
      +  "audience",
      +  "role_band",
      +  "motivation",
      +  "focus_area_ids",
      +  "success_definition",
      +  "offer_id",
      +  "context"
      +]
  6. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, and the description adds real behavioral substance: the price returned is authoritative and the agent must 'never do the arithmetic yourself', and the tool states whether the free-sessions concession applies for company deals. It does not describe error or edge-case behavior, so it falls short of a 5.

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?

Four short sentences, front-loaded with the call trigger and ending with the handoff condition; almost every clause carries a distinct instruction. The 'accumulator' label is mildly cryptic overhead, but nothing substantial is wasted.

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

Completeness4/5

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

For a ten-parameter aggregator with no output schema, the description explains what comes back (the full briefing plus two price figures and concession status) and the downstream action. It is nearly complete, though it does not address partial briefs or what happens if required fields are missing.

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 the schema already documents all ten parameters and the baseline is 3. The description maps a few of them to domain meaning (audience drives company-deal concession, offer_id is the 'chosen package', focus areas come from the taxonomy) but adds no syntax, format, or constraint detail beyond that.

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 states a specific action and artifact: it echoes the brief as a briefing covering audience, role, motivation, focus areas, success definition and chosen package, plus the catalog price and AI-channel figure. It implicitly separates itself from send_mentoring_offer (the send step) but does not name other siblings; the 'accumulator' framing is slightly abstract yet recoverable.

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?

Explicit triggers and exclusions are given: 'call after every change', read the brief back to the visitor, and only when they explicitly agree on price call send_mentoring_offer with price_agreed true. An agent knows both when to call this and when to hand off to the sibling.

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