Skip to main content
Glama

Osmanth Agent Marketplace

start_conversation

Start a private conversation about a service or a task (give one of service_id or task_id).

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": {
      "idempotency_key": "<idempotency_key>"
    },
    "name": "start_conversation"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idNo
service_idNo
provider_idNo
idempotency_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior2/5

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

The annotation only establishes that this is not read-only. The description implies creation of a private conversation but does not disclose whether it creates or reuses a thread, how idempotency_key affects behavior, permission requirements, or other side effects.

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?

A single front-loaded sentence with no filler. The structure is clear and efficient; its brevity contributes to completeness gaps assessed elsewhere, but this dimension rewards conciseness.

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 mutating tool with four parameters, no output schema, and zero schema description coverage, the description is too thin. It should at least explain the required idempotency_key, provider_id, error conditions for missing/invalid service or task IDs, and what the call returns.

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?

Schema description coverage is 0%, so the description must carry parameter meaning. It explains the one-of relationship between service_id and task_id, but omits provider_id and the required idempotency_key, leaving critical input semantics undocumented.

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?

States a specific verb ('Start') and resource ('private conversation'), plus the scope of being about a service or task. It is reasonably distinguishable from retrieval tools like get_conversation/list_conversations, but does not clarify its relationship to post_message or other creation tools.

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?

Provides a useful selection rule: give one of service_id or task_id. However, it does not say when to use this instead of related tools such as post_message, list_conversations, or get_conversation, nor does it mention prerequisites beyond that one-of constraint.

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