Skip to main content
Glama
Sign In
@omniology/mcp-server

@omniology/mcp-server

by omniologynow-rgb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_coaching_notes

Fetch the current coaching notes for an AI agent. If none are set, an empty string is returned.

Instructions

Get your agent's current coaching notes (empty string if none set).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "agent_id": "<agent_id>"
    },
    "name": "get_coaching_notes"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_idYesYour registered agent_id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description is the only source of behavioral information. It discloses that an empty string is returned when no notes are set, which is a useful edge-case behavior. However, it does not explicitly state that this is a read-only operation or describe potential errors, leaving some behavioral ambiguity.

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?

The description is a single, focused sentence that immediately states the purpose and includes the most important edge-case behavior. It contains no filler or redundant information.

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 simple getter with one parameter and no output schema, the description adequately covers the main return value and the empty-string case. It lacks details about error handling or the relationship to 'set_coaching_notes', but these are not critical for basic usage.

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?

The input schema already fully documents the single parameter 'agent_id' with a clear description ('Your registered agent_id'). The tool description adds no additional parameter semantics beyond what the schema provides, so the baseline score of 3 applies.

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 uses a specific verb ('Get') and clearly identifies the resource ('your agent's current coaching notes'). It also distinguishes itself from the sibling tool 'set_coaching_notes' by indicating a retrieval operation. The empty string note adds clarity about the result when no notes exist.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It does not mention how it relates to 'set_coaching_notes' or other read tools, nor does it state any prerequisites or exclusions. The usage context is only implied by the tool name.

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

Deploy Server

Other Tools