Skip to main content
Glama

Zoya.bg

start_conversation

Create private history only with prior user consent. No automatic chat capture.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "start_conversation"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoShopping session

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It usefully discloses the consent requirement and that chat is not captured automatically, but it does not explain what 'private history' means, whether anything is persisted, or what happens on invocation.

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?

The two sentences are short and contain no obvious filler. The privacy constraint is front-loaded, though the description could be structured around a clearer statement of the tool's action first.

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

Completeness2/5

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

For a conversation/session creation tool with no annotations and no output schema, the description is too thin. It states privacy conditions but omits core details about what starting the conversation does, what the title parameter changes, and what the caller should expect.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single optional title parameter has 0% schema description coverage, and the description does not mention it at all. It neither explains what the title controls nor clarifies the default 'Shopping session' behavior.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says 'Create private history' and emphasizes consent, but it never clearly states that the tool starts a conversation or session. The purpose is inferable rather than explicit, especially with a sibling named session_start available for comparison.

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?

It provides a clear prerequisite: use only with prior user consent. However, it does not explain when to use this tool instead of alternatives such as session_start, nor does it describe what to do when consent is absent.

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