Skip to main content
Glama
Sign In
Bunpro MCP

Bunpro MCP

by Alexxanddr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_topic_replies

Read-onlyIdempotent

Retrieve replies for a Bunpro discourse topic using its ID, with optional pagination to browse discussion threads page by page.

Instructions

Get replies for a Bunpro discourse topic

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_topic_replies"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
pageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds only domain framing ('Bunpro discourse topic') and says nothing about whether replies are paginated, what order they arrive in, or how many are returned per page — relevant since a 'page' parameter exists.

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?

A single front-loaded sentence with zero padding, which is the right shape. It is arguably too sparse rather than too verbose, but nothing in it is wasted.

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

Completeness2/5

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

With 2 undocumented parameters, no output schema, and pagination implied only by the schema, the description does not give an agent enough to call this correctly and interpret the result. It should at minimum explain the id/page contract and what a reply record contains.

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 description coverage is 0%, so the description carries the full burden, and it does not. It never clarifies whether 'id' is a topic id or a post id, and the 'page' parameter is completely unmentioned — an agent gets no signal that results are paginated or what a page yields.

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 ('Get replies') scoped to 'a Bunpro discourse topic', which is unambiguous and clearly distinct from all listed siblings (stats, SRS, vocab, search). It stops short of naming how it relates to any adjacent tool, but the resource is unique enough that no confusion is likely.

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?

No guidance on when to call this versus other tools, no prerequisites stated (e.g. that a topic id must come from a topic listing or search), and no note about paging through results. The agent must infer the entire usage context from the name.

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

Deploy Server

Other Tools