Skip to main content
Glama

MyHumanRep: Contact a Human

by com.myhumanrep
OverviewDiscussionsAdmin

Continue a conversation

continue_conversation
Idempotent

Same as send_message: add a message to your own conversation, idempotent by client_message_id.

Input Schema

NameRequiredDescriptionDefault
messageYesFollow-up message text. Max 4000 characters and 10240 UTF-8 bytes.
conversation_idYesconversation_id returned by start_conversation.
client_message_idYesRequired idempotency key, unique per conversation. Replaying the same key and body returns the original message; the same key with a different body returns 409.
conversation_tokenNoconversation_token returned once by start_conversation. Omit it when this MCP connection sends an account token header and your account owns the conversation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / conversation_token / description
      Previous value: -"conversation_token returned once by start_conversation."New value: +"conversation_token returned once by start_conversation. Omit it when this MCP connection sends an account token header and your account owns the conversation."
    • changedInput schema / required
      Previous value: -[
-  "message",
-  "client_message_id",
-  "conversation_id",
-  "conversation_token"
-]New value: +[
+  "message",
+  "client_message_id",
+  "conversation_id"
+]
  2. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, and idempotentHint=true. The description adds 'own conversation' scope and idempotency-by-client_message_id, but idempotency is also detailed in the schema and no further behavioral context (e.g., auth/token handling) is added.

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?

The description is a single efficient sentence with no wasted words. The key action is front-loaded and the sibling reference is included compactly.

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

Completeness3/5

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

The rich schema and annotations cover parameters, idempotency, and write behavior, so the description is sufficient for invocation. However, it does not clarify when to choose this tool over send_message, leaving a meaningful selection gap.

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%, so the baseline is 3. The description reinforces client_message_id idempotency but adds no parameter semantics beyond what the schema already documents.

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 states a specific action: adding a message to the caller's own conversation, and names the sibling send_message as an equivalent. It is clear what the tool does, though 'Same as send_message' equates rather than differentiates use cases.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to use continue_conversation instead of send_message, start_conversation, or other siblings. Saying 'Same as send_message' does not provide selection criteria or exclusions.

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

All MyHumanRep: Contact a Human toolsInspect
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