AI Design Blueprint Doctrine

Get My Coaching Context

me.coaching_context

Read-onlyIdempotent

Authenticated — returns stages in the caller's active course where recorded evidence is thin relative to the stage's principle requirements. Each thin stage carries the missing principle slugs + a short diagnostic so the caller can suggest the user record concrete evidence. WHEN TO CALL: when the user asks 'what should I work on next' or 'what's weak in my Blueprint progress'; before suggesting which guide/example to consult. Pair with me.add_evidence to close gaps. WHEN NOT TO CALL: to lecture the user on principles they have already satisfied; on every conversation turn (state changes only when evidence is added). BEHAVIOR: read-only, idempotent. Auth: Bearer (any plan). Returns thin_stages list with stage slug, course slug, missing principles, evidence_count, and a coaching_note.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedMay 9, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "title": "get_my_coaching_contextDictOutput",
+  "type": "object"
+}

Changed1 schema field changedMay 9, 2026

changedOutput schema / (root)

Previous value: -{
-  "$defs": {
-    "ErrorBody": {
-      "description": "The body of `error_payload(code, message, details)` returns.",
-      "properties": {
-        "code": {
-          "title": "Code",
-          "type": "string"
-        },
-        "details": {
-          "additionalProperties": true,
-          "title": "Details",
-          "type": "object"
-        },
-        "message": {
-          "title": "Message",
-          "type": "string"
-        }
-      },
-      "title": "ErrorBody",
-      "type": "object"
-    }
-  },
-  "properties": {
-    "error": {
-      "$ref": "#/$defs/ErrorBody",
-      "default": null
-    },
-    "evidence": {
-      "default": null,
-      "items": {
-        "additionalProperties": true,
-        "type": "object"
-      },
-      "title": "Evidence",
-      "type": "array"
-    },
-    "learning_path": {
-      "anyOf": [
-        {
-          "additionalProperties": true,
-          "type": "object"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "default": null,
-      "title": "Learning Path"
-    },
-    "plan": {
-      "default": null,
-      "title": "Plan",
-      "type": "string"
-    },
-    "recent_runs": {
-      "default": null,
-      "items": {
-        "additionalProperties": true,
-        "type": "object"
-      },
-      "title": "Recent Runs",
-      "type": "array"
-    },
-    "summary": {
-      "default": null,
-      "title": "Summary",
-      "type": "string"
-    },
-    "user_id": {
-      "default": null,
-      "title": "User Id",
-      "type": "string"
-    }
-  },
-  "title": "MeCoachingContextResponse",
-  "type": "object"
-}New value: +null

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$defs": {
+    "ErrorBody": {
+      "description": "The body of `error_payload(code, message, details)` returns.",
+      "properties": {
+        "code": {
+          "title": "Code",
+          "type": "string"
+        },
+        "details": {
+          "additionalProperties": true,
+          "title": "Details",
+          "type": "object"
+        },
+        "message": {
+          "title": "Message",
+          "type": "string"
+        }
+      },
+      "title": "ErrorBody",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "error": {
+      "$ref": "#/$defs/ErrorBody",
+      "default": null
+    },
+    "evidence": {
+      "default": null,
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "title": "Evidence",
+      "type": "array"
+    },
+    "learning_path": {
+      "anyOf": [
+        {
+          "additionalProperties": true,
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Learning Path"
+    },
+    "plan": {
+      "default": null,
+      "title": "Plan",
+      "type": "string"
+    },
+    "recent_runs": {
+      "default": null,
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "title": "Recent Runs",
+      "type": "array"
+    },
+    "summary": {
+      "default": null,
+      "title": "Summary",
+      "type": "string"
+    },
+    "user_id": {
+      "default": null,
+      "title": "User Id",
+      "type": "string"
+    }
+  },
+  "title": "MeCoachingContextResponse",
+  "type": "object"
+}

Changed1 schema field changedApr 28, 2026

changedOutput schema / (root)

Previous value: -{
-  "additionalProperties": true,
-  "title": "get_my_coaching_contextDictOutput",
-  "type": "object"
-}New value: +null

AddedApr 24, 2026

TDQS

A4.8/5.0

Behavior5/5

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

The description discloses behavior beyond annotations: 'BEHAVIOR: read-only, idempotent. Auth: Bearer <token> (any plan).' It also explains state-changing semantics ('state changes only when evidence is added'). This complements the readOnlyHint and idempotentHint annotations without contradicting them.

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 description is longer than average but well-structured with clear sections (main purpose, WHEN TO CALL, WHEN NOT TO CALL, BEHAVIOR, Auth, Returns). Every sentence adds value, though the auth and behavior details could be slightly condensed without losing meaning.

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?

Given the tool's complexity (zero parameters, read-only, clear output), the description is complete: it explains the output shape ('thin_stages list with stage slug, course slug, missing principles, evidence_count, and coaching_note'), auth requirements, usage triggers, and when to avoid calling. No critical information is missing.

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?

The tool has zero parameters, so there are no parameter semantics to explain. The description correctly omits parameter details, and the schema trivially covers 100% of parameters. The baseline score of 4 is appropriate for a no-parameter tool.

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?

The description clearly states the tool's function: 'returns stages in the caller's active course where recorded evidence is thin relative to the stage's principle requirements.' It uses a specific verb ('returns'), identifies the resource ('stages in the caller's active course'), and differentiates from siblings like me.add_evidence and me.learning_path by focusing on evidence thinness.

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 WHEN TO CALL and WHEN NOT TO CALL sections are provided, including example user queries ('what should I work on next'). It also explicitly names an alternative/complementary tool: 'Pair with me.add_evidence to close gaps.' This is exemplary usage guidance.

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

All AI Design Blueprint Doctrine tools Inspect

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

Need Help?