mcp-server-worldquantbrain

Overview Schema Source Related Servers Discussions Admin

List my messages

list_messages

Read-onlyIdempotent

Retrieve platform announcements or notifications, newest first, as plain text capped at 2,000 characters each, with type filtering and limit/offset pagination.

Instructions

Return platform messages, newest first, as plain text capped at 2,000 characters each.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_messages"
  }
}

Input Schema

Name	Required	Description
`type`	No	ANNOUNCEMENT or NOTIFICATION.
`limit`	No
`offset`	No

Output Schema

Name	Required	Description	Default
`count`	No
`items`	No
`next_offset`	No
`truncated_by_api`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 11, 2026

TDQS

B3.3/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, so safety is covered. The description contributes genuinely new behavioral facts: results are ordered newest first, rendered as plain text, and truncated at 2,000 characters per message — truncation in particular is a trait no annotation or schema conveys.

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?

A single sentence with no filler, and the most decision-relevant facts — resource, ordering, format, and size cap — are front-loaded. Nothing could be removed without losing information.

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

Completeness3/5

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

An output schema exists, so return shape need not be explained, and the description covers ordering and truncation well. However, for a paginated list tool with three parameters it omits how limit and offset interact, what the default page size means, and whether omitting "type" returns all message kinds.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 33%: only "type" is documented (ANNOUNCEMENT or NOTIFICATION), while limit and offset carry constraints but no prose. The description says nothing about type filtering or pagination semantics, so it fails to compensate for the coverage gap and leaves two of three parameters unexplained.

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 names a specific verb and resource ("Return platform messages") and adds ordering ("newest first"). It is clearly distinguishable from the sibling list_* tools, which target alphas, datasets, and datafields rather than messages, though it never clarifies what a "platform message" is.

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

Usage Guidelines2/5

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

There is no statement of when to call this tool, no prerequisites, and no named alternative for related needs such as unread counts or per-type filtering. The agent must infer usage entirely from the title and name.

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