Skip to main content
Glama

Mark an inbox message read

inbox_ack
Idempotent

Mark one message of your webhook inbox read (acknowledged); it stays, but inbox_messages with unread: true leaves it out. Marking it again changes nothing; unknown message_id: 404 message_not_found. To remove it, inbox_delete.

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": {
      "message_id": 42,
      "instance_id": "inb_exampleexampleexample2"
    },
    "name": "inbox_ack"
  }
}

Input Schema

NameRequiredDescriptionDefault
message_idYesThe message's id from inbox_messages.
instance_idYesUtility instance id from buy or list_utilities.
passport_tokenNoYour amp_ token, only if you have no app sign-in and cannot send a header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "instance_id": "inb_exampleexampleexample2",
      +    "message_id": 42
      +  }
      +]
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."New value: +"Your amp_ token, only if you have no app sign-in and cannot send a header."
  2. Added

TDQS

A4.7/5.0
Behavior5/5

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

While annotations cover readOnlyHint and idempotency, the description adds crucial behavioral context by explaining *how* the change manifests ('it stays, but inbox_messages with unread: true leaves it out').

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 extremely dense but highly efficient, conveying purpose, behavior, error handling, and alternatives in a single, focused passage.

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?

Given the tool's simplicity, the description is maximally complete, clarifying persistence, idempotency, and failure states without needing to explain the return structure.

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?

Since schema description coverage is 100%, the parameters are fully defined. The description adds no unique semantic meaning to the input parameters themselves, making a baseline score appropriate.

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?

The description clearly states the action (Mark read) and the resource (webhook inbox message), immediately distinguishing it from deletion or listing siblings.

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?

The definition explicitly tells the user the action is idempotent ('Marking it again changes nothing') and provides the correct alternative for removal ('To remove it, inbox_delete').

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.