Skip to main content
Glama
Sign In

Ringler

by io.ringler
OverviewDiscussionsAdmin

Get me a human

call

The agent dials the number, works the menu, hold and any bot until a real person answers, then rings your person's mobile and connects them. Spends credits ($0.30/min). If it hits voicemail it leaves a short message with a callback (default on; voicemail: skip to turn off).

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": {
      "to": "<to>",
      "target": "<target>"
    },
    "name": "call"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesPhone number, E.164 or 10 digits.
whyNoOne line on what it's about.
targetYesWho to ask for: a name or a role (the pharmacy, the front desk).
callbackNoNumber to leave: 'crew_line' (the agent's line, default), 'me', or a number.
voicemailNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing the credit cost ($0.30/min), the side effect of ringing the user's mobile, and the voicemail default with the 'voicemail: skip' opt-out. Annotations only say it is not read-only and is open-world; the description adds real operational consequences. It stops short of saying whether the call is recorded or how the outcome is reported back.

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?

Two dense sentences, front-loaded with the core action, then cost, then the voicemail default. Every clause carries operational information the agent needs; nothing is padding.

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 five-parameter, open-world, non-read-only tool with no output schema, the description covers cost, side effects, and default behaviors sufficiently to call it confidently. Minor gaps remain on what the agent receives back after the call and whether the interaction is logged.

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 80%, so the baseline is 3; the description adds genuine meaning by explaining the callback default ('crew_line'), that a voicemail is left by default, and how to disable it via voicemail: skip — details the schema's enum does not document. It does not clarify how 'target' is used when no name is known or how 'why' is spoken.

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 concrete verb and resource plus the full mechanism: dials the number, navigates menu/hold/bot, then rings the user's mobile to connect them to a human. This clearly separates it from siblings like my_calls (history) or transcript (records), so an agent knows this is the tool that performs an outbound call.

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

Usage Guidelines4/5

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

The workflow description makes the intended scenario obvious — use when the goal is to reach a live person through an IVR. It does not explicitly name when NOT to use it or point to an alternative sibling (e.g. errand or tell_me), so it falls short of full alternative routing.

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