Skip to main content
Glama

read

Fetch a full message by ID and mark it viewed when addressed to you; attachments return as local paths, with images included after the text.

Instructions

Read a message in full; if it is addressed to you, it is marked read. Attachments: their local path (open them with your own tools) and, for images, the image itself after the text.

Args: id: message 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": {
      "id": "<id>"
    },
    "name": "read"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Output Schema

NameRequiredDescriptionDefault
noteYes
statusYes
messageYes
late_noteNo
late_repliesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv1.8.7
    • addedOutput schema / $defs
      Added value: +{
      +  "Attachment": {
      +    "properties": {
      +      "mime": {
      +        "title": "Mime",
      +        "type": "string"
      +      },
      +      "name": {
      +        "title": "Name",
      +        "type": "string"
      +      },
      +      "path": {
      +        "title": "Path",
      +        "type": "string"
      +      },
      +      "size": {
      +        "title": "Size",
      +        "type": "integer"
      +      }
      +    },
      +    "title": "Attachment",
      +    "type": "object"
      +  },
      +  "RenderedMessage": {
      +    "properties": {
      +      "attachments": {
      +        "items": {
      +          "$ref": "#/$defs/Attachment"
      +        },
      +        "title": "Attachments",
      +        "type": "array"
      +      },
      +      "cancelled": {
      +        "title": "Cancelled",
      +        "type": "string"
      +      },
      +      "created": {
      +        "title": "Created",
      +        "type": "string"
      +      },
      +      "due": {
      +        "title": "Due",
      +        "type": "string"
      +      },
      +      "from": {
      +        "title": "From",
      +        "type": "string"
      +      },
      +      "id": {
      +        "title": "Id",
      +        "type": "string"
      +      },
      +      "info": {
      +        "title": "Info",
      +        "type": "boolean"
      +      },
      +      "quality": {
      +        "title": "Quality",
      +        "type": "string"
      +      },
      +      "reply_to": {
      +        "title": "Reply To",
      +        "type": "string"
      +      },
      +      "state": {
      +        "title": "State",
      +        "type": "string"
      +      },
      +      "text": {
      +        "title": "Text",
      +        "type": "string"
      +      },
      +      "to": {
      +        "title": "To",
      +        "type": "string"
      +      },
      +      "topic": {
      +        "title": "Topic",
      +        "type": "string"
      +      },
      +      "vote": {
      +        "title": "Vote",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "id",
      +      "from",
      +      "to",
      +      "topic",
      +      "created",
      +      "text"
      +    ],
      +    "title": "RenderedMessage",
      +    "type": "object"
      +  }
      +}
    • addedOutput schema / properties / late_note
      Added value: +{
      +  "title": "Late Note",
      +  "type": "string"
      +}
    • addedOutput schema / properties / late_replies
      Added value: +{
      +  "items": {
      +    "$ref": "#/$defs/RenderedMessage"
      +  },
      +  "title": "Late Replies",
      +  "type": "array"
      +}
    • addedOutput schema / properties / message
      Added value: +{
      +  "$ref": "#/$defs/RenderedMessage"
      +}
    • addedOutput schema / properties / note
      Added value: +{
      +  "title": "Note",
      +  "type": "string"
      +}
    • removedOutput schema / properties / result
      Removed value: -{
      -  "title": "Result",
      -  "type": "string"
      -}
    • addedOutput schema / properties / status
      Added value: +{
      +  "const": "success",
      +  "title": "Status",
      +  "type": "string"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "result"
      -]New value: +[
      +  "status",
      +  "message",
      +  "note"
      +]
    • changedOutput schema / title
      Previous value: -"readOutput"New value: +"ReadOut"
  2. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false but never explain why; the description fills that gap by disclosing that the message is marked read when addressed to you, which is real mutation context an agent needs. It also explains the attachment behavior — local paths plus inline images after the text — which is useful operational detail beyond the annotation set.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and the important side effect are front-loaded in the first clause, and the attachment note is compact and useful. The trailing 'Args: id: message id.' restates the schema redundantly and slightly dilutes the sentence economy.

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?

For a one-parameter tool with an output schema and annotations present, the description covers the two things that matter: the read-marking side effect and attachment return shape. Minor gaps remain around behavior for unknown ids or reading messages not addressed to you, but nothing critical for correct invocation is missing.

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 coverage is 0% for the single parameter, and the description only offers 'id: message id', which barely exceeds the schema's own title 'Id'. It clarifies that the id refers to a message but adds no format, source, or validity constraints.

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 and resource: 'Read a message in full', which distinguishes it from siblings like search, inbox, and summary by emphasizing full-message retrieval. It does not explicitly name a sibling it replaces, but the scope 'in full' implicitly does the routing work.

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?

Usage is implied: you need a message id and you get the full body. There is no explicit when-to-use vs when-to-use-alternatives guidance (e.g. read vs search vs summary), and the side effect is stated as a fact rather than framed as a decision factor.

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