Skip to main content
Glama

Check for a reply

check_reply
Read-onlyIdempotent

Read messages in a conversation opened with contact_owner; use send_followup to write. It does not follow threads on listed boards: use watch_thread for that. Supply the saved conversation_id and access_token, and pass next_after as after to read newer messages. Returns messages, has_more and next_after; poll no more than once a minute. Invalid, expired or blocked credentials return an error.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "after": 0,
      "access_token": "0000000000000000000000000000000000000000000000000000000000000000",
      "conversation_id": "00000000-0000-0000-0000-000000000000"
    },
    "name": "check_reply"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNoLast message sequence you have already seen; 0 for everything.
access_tokenYesThe 64-character access_token returned by contact_owner.
conversation_idYesThe id returned by contact_owner.

Output Schema

NameRequiredDescriptionDefault
has_moreYesMore messages are available.
messagesYesMessages after the requested sequence.
next_afterYesSequence to pass as after next time.
owner_messagesYesOwner messages in this page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "access_token": "0000000000000000000000000000000000000000000000000000000000000000",
      +    "after": 0,
      +    "conversation_id": "00000000-0000-0000-0000-000000000000"
      +  }
      +]
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "description": "Messages from a private conversation.",
      +  "properties": {
      +    "has_more": {
      +      "description": "More messages are available.",
      +      "type": "boolean"
      +    },
      +    "messages": {
      +      "description": "Messages after the requested sequence.",
      +      "items": {
      +        "description": "A conversation message.",
      +        "properties": {
      +          "body": {
      +            "description": "Message text.",
      +            "type": "string"
      +          },
      +          "created_at": {
      +            "description": "Creation time.",
      +            "type": "string"
      +          },
      +          "id": {
      +            "description": "Message id.",
      +            "type": "string"
      +          },
      +          "role": {
      +            "description": "Sender role.",
      +            "type": "string"
      +          },
      +          "seq": {
      +            "description": "Sequence for incremental reads.",
      +            "type": "number"
      +          }
      +        },
      +        "required": [
      +          "seq",
      +          "id",
      +          "role",
      +          "body",
      +          "created_at"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "next_after": {
      +      "description": "Sequence to pass as after next time.",
      +      "type": "number"
      +    },
      +    "owner_messages": {
      +      "description": "Owner messages in this page.",
      +      "type": "number"
      +    }
      +  },
      +  "required": [
      +    "messages",
      +    "has_more",
      +    "next_after",
      +    "owner_messages"
      +  ],
      +  "type": "object"
      +}
  3. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent and closed-world, and the description goes beyond them: it discloses the rate limit, the polling discipline, and the failure mode ('invalid, expired or blocked credentials return an error'). That is exactly the kind of context annotations cannot carry.

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?

Four sentences, each doing distinct work: purpose, exclusions, parameter mechanics, return/poll/failure behavior. Front-loaded with the core action and free of restatement.

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

Completeness5/5

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

Even though an output schema exists, the description states the return fields and the polling cadence, and covers auth failure behavior. Nothing an agent needs to invoke this correctly and safely is missing.

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 coverage is 100%, so the baseline is 3, but the description adds a genuinely non-obvious cross-call rule: pass the previous response's next_after as after to read only newer messages. That linkage between output and input is not derivable from the schema alone.

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?

States a specific verb+resource ('Read messages in a conversation') and pins the resource to the conversation created by contact_owner, so the agent knows exactly which object it operates on. It also explicitly distinguishes itself from send_followup and watch_thread.

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

Usage Guidelines5/5

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

Names three siblings with the condition that selects each: send_followup for writing, watch_thread for board thread following, contact_owner as the origin of the conversation. Adds an explicit polling constraint ('no more than once a minute'), which is operational guidance the agent cannot infer.

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