Skip to main content
Glama

cd_raw

cd_raw
Read-only

Fetches a Chief Delphi thread as plain Discourse markdown with per-post author and timestamp headers, and supports post ranges and character limits to keep replies small.

Instructions

Fetch a Chief Delphi thread as plain Discourse markdown (the /raw endpoint) — the cheapest way to read a whole discussion, with author and timestamp headers per post and image references left as upload:// tokens. Read only part of a long thread with start_post/end_post to keep the reply small.

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": {
      "topic": "<topic>"
    },
    "name": "cd_raw"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYesNumeric topic id.
end_postNoLast post number to include (needs start_post).
max_charsNoCap the reply at this many characters (default 20000).
start_postNoFirst post number to include.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the read-only and open-world safety profile, so the description is free to add real behavioral detail, and it does: per-post author/timestamp headers, image references degraded to upload:// tokens (a non-obvious caveat that changes what the agent can do with results), and the size-control purpose of the post range. It omits any mention of the max_chars truncation behavior or what happens when the cap is hit.

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?

Two sentences, front-loaded with what the tool returns and why it is cheap, followed by the narrowing tactic. Every clause carries information; nothing is redundant or padded.

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 no output schema, the description does the work of describing the return shape (markdown with per-post headers and upload:// image tokens), which is exactly what an agent needs. The one gap is truncation semantics — max_chars caps the reply but the description never says what a capped response looks like or how to continue from it.

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 description coverage is 100%, so all four parameters are already documented, including the 'needs start_post' dependency on end_post and the 20000 default. The description only reinforces the start/end pair with a rationale (keep the reply small) and says nothing about topic or max_chars, so it adds marginal meaning beyond the schema — baseline 3.

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 gives a specific verb and resource ('Fetch a Chief Delphi thread'), names the exact representation ('plain Discourse markdown, the /raw endpoint'), and positions it economically ('the cheapest way to read a whole discussion'). The format and cost framing distinguish it from the structured-metadata siblings like cd_topic without needing to name them.

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?

It clearly states the use case (reading a whole discussion cheaply) and gives a concrete tactic for when the thread is long: use start_post/end_post to keep the reply small. What's missing is an explicit exclusion — it never says when to prefer a structured sibling or when the raw view is the wrong choice.

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