Skip to main content
Glama

mentoring-inquiry-builder

by coach.marian
OverviewDiscussionsAdmin

Lay out the dated session program for a package

design_mentoring_program
Read-onlyIdempotent

Deterministic session skeleton computed from the package's cadence metadata: dated sessions, each with its planned theme (diagnostic, the visitor's focus areas — pass focus_area_ids — the mid-point checkpoint, operational to strategic, the closing review against the definition of success). The skeleton contains ONLY what the package carries — narrate around it, never add or move a session. Dates are planning targets; the intro call fixes the real schedule. Call when the visitor asks what the engagement actually looks like.

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.
offer_idNoRequired. One of: single-session, first-quarter, monthly, mentor-in-residence, mentor-in-residence-2day.
start_dateNoRequired. First session date, YYYY-MM-DD, today or later (ask the visitor; default to next Monday)
leaders_countNoCompany deals: how the pooled sessions are shared. Changes the allocation note, never the schedule.
focus_area_idsNoAgreed focus area ids in priority order. They become the planned themes of the focus sessions; without them those sessions read as open.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / focus_area_ids
      Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "string"
+    }
+  ],
+  "description": "Agreed focus area ids in priority order. They become the planned themes of the focus sessions; without them those sessions read as open."
+}
  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. Changed9 schema fields changed
    • 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"
    • 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"
-]
    • changedInput schema / properties / start_date / description
      Previous value: -"First session date, YYYY-MM-DD, today or later (ask the visitor; default to next Monday)"New value: +"Required. First session date, YYYY-MM-DD, today or later (ask the visitor; default to next Monday)"
    • removedInput schema / required
      Removed value: -[
-  "offer_id",
-  "start_date",
-  "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: -[
-  "offer_id",
-  "start_date"
-]New value: +[
+  "offer_id",
+  "start_date",
+  "context"
+]
  6. Changed2 schema fields changed
    • addedInput schema / properties / leaders_count
      Added value: +{
+  "description": "Company deals: how the pooled sessions are shared. Changes the allocation note, never the schedule.",
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}
    • changedInput schema / properties / start_date / description
      Previous value: -"First session date, YYYY-MM-DD (ask the visitor; default to next Monday)"New value: +"First session date, YYYY-MM-DD, today or later (ask the visitor; default to next Monday)"
  7. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses the key behavioral constraints: it is deterministic, it contains ONLY what the package carries, you must never add or move a session, and dates are planning targets that the intro call later fixes. Those are exactly the behavioral traits an agent needs and that annotations cannot convey.

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?

Front-loaded with the deterministic-skeleton purpose, and every clause earns its place by constraining behaviour. It is dense with parentheticals and runs long for a single paragraph, but there is no filler.

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?

With no output schema, the description carries the burden of describing the return, and it does so adequately by enumerating the session themes (diagnostic, focus areas, mid-point checkpoint, closing review). It could be clearer on exact return shape, but an agent has enough to call it correctly.

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 genuinely adds meaning: focus_area_ids become the planned themes of focus sessions and leave them 'open' when absent, and leaders_count changes only the allocation note, never the schedule. That maps parameter effects to output consequences rather than restating the schema.

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?

It names a specific verb+resource: 'Deterministic session skeleton computed from the package's cadence metadata' producing 'dated sessions, each with its planned theme.' This is clearly distinct from the booking/compose siblings, though no sibling is named to sharpen the boundary.

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?

It gives an explicit trigger — 'Call when the visitor asks what the engagement actually looks like' — and frames the output as a planning artifact rather than a booking. No alternative tool is named for the adjacent cases (e.g. when to book versus plan), so it stops short of full when/when-not guidance.

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

All mentoring-inquiry-builder toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources