Skip to main content
Glama

Read message

get_message_content
Destructive

Get a message's full text and attachments. Opening a received message marks it read in Librus, as the app does. A server can require consent for that: on CONSENT_REQUIRED, ask the user, then call again with allow_mark_read=true.

Instructions

Get a message's full text and attachments. Opening a received message marks it read in Librus, as the app does. A server can require consent for that: on CONSENT_REQUIRED, ask the user, then call again with allow_mark_read=true. Archived messages cannot be opened.

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": {
      "account_alias": "<account_alias>",
      "message_ref": "<message_ref>"
    },
    "name": "get_message_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
message_refYesA message's reference from get_messages.
account_aliasYesLogin alias from list_accounts.
allow_mark_readNofalse leaves a received message unread and unopened.

Output Schema

NameRequiredDescriptionDefault
dataYes
backendYes
contextYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv2.8.1
    • changedOutput schema / $defs / MessageTimestamp / properties / local / pattern
      Previous value: -"^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}(?:\\.[0-9]{1,6})?(?:Z|[+-][0-9]{2}:[0-9]{2})?$"New value: +"^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}(\\.[0-9]{1,6})?(Z|[+-][0-9]{2}:[0-9]{2})?$"
    • changedOutput schema / $defs / ModernMessageRecipientReceipt / properties / read_at / anyOf
      Previous value: -[
      -  {
      -    "pattern": "^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}(?:\\.[0-9]{1,6})?(?:Z|[+-][0-9]{2}:[0-9]{2})?$",
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "pattern": "^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}(\\.[0-9]{1,6})?(Z|[+-][0-9]{2}:[0-9]{2})?$",
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedOutput schema / $defs / ModernMessageSummary / properties / read_at / anyOf
      Previous value: -[
      -  {
      -    "pattern": "^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}(?:\\.[0-9]{1,6})?(?:Z|[+-][0-9]{2}:[0-9]{2})?$",
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "pattern": "^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}(\\.[0-9]{1,6})?(Z|[+-][0-9]{2}:[0-9]{2})?$",
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedOutput schema / $defs / ModernMessageSummary / properties / sent_at / pattern
      Previous value: -"^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}(?:\\.[0-9]{1,6})?(?:Z|[+-][0-9]{2}:[0-9]{2})?$"New value: +"^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}(\\.[0-9]{1,6})?(Z|[+-][0-9]{2}:[0-9]{2})?$"
    • changedOutput schema / $defs / Observation / properties / observed_at / pattern
      Previous value: -"^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}(?:\\.[0-9]{1,6})?(?:Z|[+-][0-9]{2}:[0-9]{2})?$"New value: +"^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}(\\.[0-9]{1,6})?(Z|[+-][0-9]{2}:[0-9]{2})?$"
  2. Changed4 schema fields changedv2.5.1
    • addedInput schema / properties / allow_mark_read / anyOf
      Added value: +[
      +  {
      +    "type": "boolean"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / allow_mark_read / default
      Previous value: -falseNew value: +null
    • changedInput schema / properties / allow_mark_read / description
      Previous value: -"Consent to mark a received message read."New value: +"false leaves a received message unread and unopened."
    • removedInput schema / properties / allow_mark_read / type
      Removed value: -"boolean"
  3. Changed1 schema field changedv2.5.0
    • removedOutput schema / additionalProperties
      Removed value: -false
  4. Changed5 schema fields changedv2.3.1
    • changedInput schema / $defs / MessageReferenceInput / properties / account / pattern
      Previous value: -"^(?:[^\\s\\x00-\\x1f\\x7f]|[^\\s\\x00-\\x1f\\x7f](?:[^\\s\\x00-\\x1f\\x7f]| )*[^\\s\\x00-\\x1f\\x7f])$"New value: +"^[^\\s\\x00-\\x1f\\x7f](?: *[^\\s\\x00-\\x1f\\x7f])*$"
    • addedInput schema / properties / account_alias / description
      Added value: +"Login alias from list_accounts."
    • changedInput schema / properties / account_alias / pattern
      Previous value: -"^(?:[^\\s\\x00-\\x1f\\x7f]|[^\\s\\x00-\\x1f\\x7f](?:[^\\s\\x00-\\x1f\\x7f]| )*[^\\s\\x00-\\x1f\\x7f])$"New value: +"^[^\\s\\x00-\\x1f\\x7f](?: *[^\\s\\x00-\\x1f\\x7f])*$"
    • addedInput schema / properties / allow_mark_read / description
      Added value: +"Consent to mark a received message read."
    • addedInput schema / properties / message_ref / description
      Added value: +"A message's reference from get_messages."
  5. First observed

TDQS

A4.6/5.0
Behavior5/5

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

It discloses the non-obvious side effect that a read nominally behaves like a mutation (marking the message read in Librus), names the exact error code CONSENT_REQUIRED, and describes the recovery path with allow_mark_read=true. This is consistent with destructiveHint=true and readOnlyHint=false and adds genuine context beyond them, including the hard restriction on archived messages.

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?

Three short sentences, each carrying distinct information: what is returned, what side effect occurs, and what the error/consent flow plus the archived exclusion are. The side effect is front-loaded rather than buried, and there is no redundant restatement of the name or title.

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

Completeness4/5

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

With an output schema present, the description need not explain return values, and the safety/error profile is covered thoroughly. The remaining gap is the attachment handling: the definition does not say whether attachments are downloaded inline or must be fetched with download_attachment.

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 goes further by explaining when to set allow_mark_read=true (only after user consent on CONSENT_REQUIRED), which the schema's "false leaves a received message unread and unopened" does not convey. The message_ref parameter is only explained via its schema cross-reference to get_messages.

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?

"Get a message's full text and attachments" gives a specific verb plus resource and scope, which cleanly separates it from the sibling list operation get_messages. An agent can tell without opening the schema that this is the single-message detail reader rather than a listing call.

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

Usage Guidelines4/5

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

The description states the conditions that govern invocation well: opening a received message marks it read, consent may be required, and archived messages cannot be opened at all. It stops short of clarifying how attachments relate to the sibling download_attachment tool, leaving a small but real ambiguity about whether attachments are returned or merely referenced.

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