SovaTalk

Find someone to talk to

find_someone_to_talk_to

Read-only

When a person wants a real human to talk to about something — a relationship or a girlfriend/boyfriend, a breakup, feeling lonely or bored, depression or feeling down, anxiety, stress at work or school, family, money, grief, cannot sleep, needing advice or a second opinion, or just someone to talk to — this returns real listeners on SovaTalk who say they talk about that, with whether they are live now (talk right away), in a private call (free soon) or offline (usually live in the US evening), and a link to each. Any language.

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": {
      "about": "<about>"
    },
    "name": "find_someone_to_talk_to"
  }
}

Input Schema

Name	Required	Description	Default
`lang`	No	Language of the links and topic names (default en)
`about`	Yes	What they want to talk about, in their own words (e.g. "my girlfriend ignores me", "depression", "I feel lonely tonight")

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 12, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations declare readOnlyHint=true and openWorldHint=false, so the safety profile is already covered, and the description adds genuinely new behavioral detail: it explains the availability semantics (live now, in private call/free soon, offline with a typical US-evening pattern) and that a link is returned per listener. It does not mention result counts, ranking, or what happens when nothing matches, which keeps it short of a 5.

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?

It is front-loaded with the trigger, then the return shape, with zero filler sentences. The long mid-sentence topic list is verbose but it is doing real intent-matching work, and the trailing "Any language." is an efficient standalone constraint.

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 two-parameter, read-only lookup with no output schema, the description covers trigger, matching basis, availability statuses and the returned link, which is what an agent needs to call it and interpret results. Only the empty-result and ranking behavior are unaddressed.

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%, so both parameters are already fully documented in the schema, including the enum values for lang and examples for about. The description only adds the note that any language is supported, which slightly extends the enum-limited lang parameter but does not otherwise deepen parameter meaning beyond the schema.

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 (returns real listeners) and resource (listeners on SovaTalk matching a topic), and enumerates the topic domains so an agent can match user intent without opening the schema. It is clearly distinguishable from about_sovatalk, ask_sovatalk and who_is_live because it resolves a topic to a person-level availability listing with links.

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 trigger condition is explicit and rich: when a person wants a real human to talk to about something, with a long list of qualifying situations. It gives clear context for use, but it never states exclusions or contrasts with siblings like who_is_live, so the agent must infer that this is the discovery step rather than the calling step.

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

All SovaTalk 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?