SovaTalk

Ask SovaTalk

ask_sovatalk

Read-only

Ask SovaTalk's own assistant anything about the site — prices, how calls work, privacy, safety, payments — and get an answer from the site's real rules, with links.

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": {
      "question": "<question>"
    },
    "name": "ask_sovatalk"
  }
}

Input Schema

Name	Required	Description	Default
`lang`	No	Answer language (default en)
`question`	Yes	The question, in plain language

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety and scope profile is covered. The description adds that answers are grounded in 'the site's real rules' and include links, which is genuine behavioral context, but it says nothing about fallback behavior for unanswerable questions or any limits on what the assistant will cover.

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?

One front-loaded sentence with the verb and resource first, then the topic scope and answer characteristics. The topic list earns its place by defining coverage, though 'SovaTalk's own assistant' is slightly redundant with the tool name.

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 simple two-parameter, read-only Q&A tool with no output schema, the description conveys what it answers, the topical scope, and that answers come with links to source material. The main missing piece is guidance on questions the assistant cannot answer or on how to route to the static-info siblings.

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 description coverage is 100% with only two parameters, including a documented enum for the answer language, so the schema carries parameter meaning. The description does not add syntax, length, or phrasing guidance for the question parameter, so baseline 3 applies.

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?

The description names a specific verb (ask) and a specific resource (SovaTalk's own assistant / site knowledge), and enumerates covered topics: prices, how calls work, privacy, safety, payments. It does not explicitly contrast with siblings like about_sovatalk, so an agent must infer the boundary between 'ask a question' and 'get static info'.

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

Usage Guidelines3/5

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

Usage is implied: pose a natural-language question about the site and receive a grounded answer. There is no explicit when-to-use vs when-not guidance, no mention of when a sibling such as about_sovatalk or who_is_live would be preferable, and no statement about off-topic questions.

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?