OTP

Get your coaching observations

my_coaching

Read-only

What needs attention for the person asking: observations OTP has computed about the seats they hold, each with the suggested next actions attached. Returns only their own seats -- never a colleague's, never a direct report's. Answers with what the evaluation engine actually wrote; if it has not run there is nothing to report and the tool says so rather than estimating. ALSO returns openQuestions: things only this person can tell OTP, which it cannot observe. When any are present, say which part of the picture is missing and ask ONE of them conversationally at the end of your answer -- never a list, never all of them, and never before you have answered what they actually asked. Record the reply with answer_coaching_question.

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

Input Schema

Name	Required	Description	Default
`question`	No	The person's question in their own words, e.g. 'what should I fix first?'. Steers what to lead with; never changes what exists.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 30, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already mark this as a safe read-only operation, but the description adds important behavioral details: it only returns the caller's own seats, it reports only what the evaluation engine actually wrote, and if the engine has not run it says so rather than estimating. It also discloses that openQuestions are things only the caller can tell OTP.

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 front-loaded with the tool's purpose and then adds necessary behavioral guidance. It is somewhat long, but each part carries useful context about scope, limitations, and handling openQuestions.

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 compensates by explaining what the tool returns, how it behaves when the evaluation engine has not run, and how to handle openQuestions. Combined with complete schema coverage for the only parameter, an agent has enough context to call and use the tool correctly.

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 single optional question parameter is already well documented in the schema. The description does not add meaning beyond the schema for that parameter, which is the baseline when schema coverage is high.

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 states a specific resource and scope: coaching observations about the caller's own seats, with suggested next actions. It also distinguishes the tool's scope by saying it returns only their own seats, never a colleague's or direct report's, which helps separate it from sibling coaching and seat-related tools.

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?

It gives explicit behavioral guidance for using the tool's output: if openQuestions are present, say what part of the picture is missing and ask exactly one conversationally at the end, never as a list and never before answering the user's actual question. It also names answer_coaching_question as the follow-up tool for recording replies.

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

All OTP 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?