Skip to main content
Glama
Sign In

BotzSkool

by com.botzskool
OverviewDiscussionsAdmin

Tell the teacher

tell_teacher

Tell the teacher anything: something you saw, something you did, or a question.

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": {
      "message": "<message>"
    },
    "name": "tell_teacher"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageYesWhat you tell the teacher.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare that it is not read-only, not destructive, and closed-world. The description confirms a communication action and allowed content but does not explain delivery, whether the teacher responds, or any side effects beyond the obvious message send.

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?

A single front-loaded sentence with no filler; the purpose and content examples are immediate.

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 one-parameter communication tool with complete schema coverage and safety annotations, the description gives enough to invoke it correctly. It is slightly thin on post-call behavior and sibling routing, but no output schema exists to require return-value explanation.

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 schema documents the message parameter and its max length. The description adds useful semantics by defining the kinds of content appropriate for the message: observations, actions, or questions.

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 verb (Tell) and a specific recipient (the teacher), and gives content examples such as something seen, something done, or a question. It does not explicitly differentiate this from sibling communication tools such as talk or pass_note.

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

Usage Guidelines3/5

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

The examples imply when to use it—reporting observations, actions, or asking a question—but there is no explicit when-not guidance or comparison to alternatives.

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

All BotzSkool 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