Skip to main content
Glama
Sign In

Ringler

by io.ringler
OverviewDiscussionsAdmin

Leave word for my person

tell_me

Send your person a spoken message through their agent. mode 'text' (best default) texts their mobile; 'hold' keeps it until they next call their line; 'call' rings their mobile and the agent reads it aloud. Their reply by text lands in my_messages. Use 'call' only when they asked to be rung, or for something that can't wait. Calls spend credits.

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_me"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNo
messageYesWhat to tell them, plainly.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / message / description
      Previous value: -"What to tell them, plainly, as the agent will say it aloud."New value: +"What to tell them, plainly."
    • changedInput schema / properties / mode / enum
      Previous value: -[
-  "hold",
-  "call"
-]New value: +[
+  "text",
+  "hold",
+  "call"
+]
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false and openWorldHint=true, and the description adds real value on top: calls spend credits, 'hold' defers delivery until the recipient next checks in, and replies route to my_messages. It stops short of saying whether a delivery confirmation or failure state is surfaced, which would matter for a message that leaves the system.

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?

Three dense sentences with no filler; the primary action comes first, modes second, guidance and cost last. Every clause carries information the agent needs.

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?

Only two parameters, no output schema, and the description covers modes, cost, delivery timing, and where replies land — nearly everything needed to call it correctly. The one gap is the unspecified default when mode is omitted.

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 50% and the enum values carry no descriptions in the schema, so the description does the heavy lifting by defining what text/hold/call each do. Minor ambiguity: it calls 'text' the 'best default' without confirming that omitting mode yields text, since the schema declares no default value.

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?

States a specific verb and resource: 'Send your person a spoken message through their agent.' The three delivery modes are spelled out, so an agent reading only the description knows exactly what the tool does and how it differs from read-only siblings like my_messages.

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 default recommendation ('text' is 'best default'), an explicit exclusion for 'call' ('only when they asked to be rung, or for something that can't wait'), and a cost caveat. This is genuine when/when-not guidance rather than implied usage.

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

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