bots

Chat with a live URBot bot

chat_with_bot

Send a message to a live URBot expert bot and get its reply (with emotion metadata). Works without an account via the free preview (a few messages per bot per session); purchased bots or an URBOT_API_KEY lift the limits. Pass the returned session_id back in to continue the same conversation. Example slugs: chef, medic, professor, legal, hunter, blender.

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": {
      "slug": "<slug>",
      "message": "<message>"
    },
    "name": "chat_with_bot"
  }
}

Input Schema

Name	Required	Description
`slug`	Yes	Bot slug, e.g. "chef"
`message`	Yes	Your message to the bot
`session_id`	No	Session id from a previous reply, to continue that conversation

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 10, 2026

TDQS

A4.2/5.0

Behavior3/5

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

No annotations provided, so description carries the burden. Discloses free preview limitations and emotion metadata. Lacks details on rate limits, response format, or potential errors, but for a simple chat tool it is adequate.

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?

Description is concise (5 sentences) with no fluff. Front-loads the main action, then provides usage limitations, continuation hint, and examples. Every sentence earns its place.

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?

Given no annotations and no output schema, the description adequately covers purpose, usage context, parameter hints, and statefulness. Could be slightly more explicit about the reply structure, but overall sufficient for a simple tool.

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 covers all 3 parameters with descriptions. The tool description adds value by providing example slugs and clarifying that session_id is used to continue the conversation, which goes beyond the schema's description.

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?

Description clearly states the verb 'Send a message' and resource 'live URBot expert bot', mentions emotion metadata in reply, and is distinct from sibling tools which are about getting bot info or listing/searching bots.

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?

Provides context on when to use: free preview limits, lifted with purchased bots or API key; also explains how to continue a conversation by passing session_id. No explicit when-not-to-use, but siblings are sufficiently different to imply usage.

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

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