Skip to main content
Glama
inboxd
by 47star

get_message

Retrieve a single local message or work record by ID, reading its body in bounded segments via offset and length and optionally including sender and source metadata.

Instructions

Read one local record with a bounded body segment, sender name and source metadata.

Use an ID returned by a query. offset and length count Unicode characters, not bytes. Follow next_request until next_offset is null for the remaining body. Raw transport payloads are omitted; they remain stored locally. Sender names reflect the latest collected profile. Work-item and source bodies are readable text including comments. Full metadata and original markup are opt-in via metadata_request or include_metadata=true, avoiding repeated large metadata on each body page. Offsets refer to the returned text representation.

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": "get_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
lengthNo
offsetNo
include_metadataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that raw transport payloads are omitted but still stored locally, that sender names reflect the latest profile (not the historical snapshot), and that offsets refer to the returned text representation. It does not cover what happens on an unknown ID or how errors surface.

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?

Every sentence carries information and the core contract (bounded body read plus pagination loop) is front-loaded. It is dense but not padded; the closest thing to waste is the metadata_request mention, which should be reconciled with the actual parameter name.

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 4-parameter, no-annotation, no-output-schema tool, the description covers the pagination protocol, the character-counting semantics, and what is intentionally excluded from the response. Gaps remain around the error path for an invalid ID and the exact shape of next_request, which an agent must discover at runtime.

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 0%, so the description must compensate, and it does for the critical parts: offset and length count Unicode characters rather than bytes, offset is relative to the returned text rather than the raw source, and include_metadata gates the expensive payload. It also references 'metadata_request', which is not a parameter in this schema, creating avoidable confusion about what to actually send.

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 verb and resource ('Read one local record with a bounded body segment, sender name and source metadata') and notes the ID comes from a prior query, which separates it from list/search siblings. It never explicitly says 'message' versus 'record' though, so an agent must infer the resource type from the tool name.

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?

It gives a clear precondition ('Use an ID returned by a query') and a follow-up rule ('Follow next_request until next_offset is null'), which is implied usage rather than explicit when-to-use guidance. It names no alternative for the case where the caller has no ID, so an agent must guess that search_messages or get_recent_records is the entry point.

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