AI Anyone

Call this person

call_person

Read-onlyIdempotent

Use this when someone wants to talk to a person out loud, hear their voice or call them: "can I call Einstein", "I want to hear Marcus Aurelius say it", "let me talk to Cleopatra out loud". Returns a call card with one button that opens a live voice call with that person on AI Anyone, in the browser. They pick up when you call.

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": {
      "mind_id": "<mind_id>"
    },
    "name": "call_person"
  }
}

Input Schema

Name	Required	Description	Default
`mind_id`	Yes	The person id, for example "albert-einstein". Use find_someone_to_ask if unsure.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 30, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/idempotent/non-destructive, and the description is consistent with that by explaining it returns a card rather than initiating a call itself. It adds useful context (browser-based, person picks up on call) beyond the annotations, though it says nothing about failure modes if the person is unavailable.

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

Conciseness4/5

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

Front-loaded with the usage condition, then the return behavior. The three quoted examples are slightly repetitive but each demonstrates a distinct phrasing, so they mostly earn their place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, and the description compensates by describing the return value (a call card with one button). For a one-parameter read-only tool, nothing an agent needs to call it correctly is missing.

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?

Single parameter with 100% schema coverage, including an example value and a pointer to find_someone_to_ask. The description adds no additional semantics for mind_id, so the schema carries the load, which is appropriate at this coverage level.

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 (call) and resource (a person), and immediately clarifies the outcome: a call card that opens a live browser voice call. That distinguishes it from siblings like speak_as_person and find_someone_to_ask, which are text/selection tools.

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 concrete trigger utterances ("can I call Einstein", "let me talk to Cleopatra out loud") and routes id lookup to find_someone_to_ask via the schema. It never explicitly contrasts with speak_as_person, which is the closest sibling, so the when-not guidance is incomplete.

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

All AI Anyone tools Inspect

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

Need Help?