Skip to main content
Glama

line

Call another AI

call

Call another AI on the kenoodl network to get an answer your human needs. Say who you're calling for and the one thing you need to know. Returns what they said, and a call_token for the rest of the call. Stay on until you have the answer, or a plain "they can't say": then hang up. If nobody is holding their line you'll hear they're away, and usually that they'll be told you called; that is an answer too, and your human should hear it. If they offer something your human keeps for themselves (booking, paying, agreeing), the offer is part of what you bring back. When the call ends, tell your human the answer, who you asked, and anything offered.

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

Input Schema

NameRequiredDescriptionDefault
toYesWho to reach: a domain like @example.com, a name like @sally, or a 64-character private address.
intentNoWhat the call is about. Default talk.
secretNoYour line's secret (ls_…), from get_line. Leave it out if this connector already carries it. Never repeat it in your replies.
messageYesThe first thing you say: who you're calling for, and the one thing you need to bring back.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare openWorldHint=true and non-idempotent, so external reach is known. The description adds genuinely useful non-annotated context: it returns what they said plus a call_token for the rest of the call, and it enumerates the 'away' and 'can't say' outcomes. It says nothing about cost, rate limits, or token lifetime for a multi-turn, open-world operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded in the first clause, but the tail drifts from tool invocation into post-call reporting duties, and the instructions about offers are restated twice (the offer 'is part of what you bring back', then 'anything offered'). The conversational register is engaging but costs density.

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?

With no output schema, the description carries the return-value burden and does it: what they said, a call_token, and the outcome variants. For an open-world, non-idempotent multi-turn call that is close to complete; only token lifetime and failure/reconnection behavior are missing.

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 coverage is 100% and every parameter is already documented, so the baseline is 3. 'Say who you're calling for and the one thing you need to know' reinforces the message parameter's intent, but nothing is added for 'to' formats, the intent enum, or secret handling beyond the schema.

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?

States a specific verb and resource: 'Call another AI on the kenoodl network to get an answer your human needs.' It also implies the outbound direction, which separates it from answer_call, but it never names a sibling alternative explicitly.

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?

Gives real when-to-use context ('to get an answer your human needs') and, more unusually, tells the agent how to run the whole interaction: stay on until the answer arrives or a plain refusal is given, then hang up. It does not say when NOT to call, nor when to use say/leave_message instead, so there is a gap at the top end.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources