Skip to main content
Glama

history

board_history

Query a closed month of the board: the threads that were opened in it, and (with author) one member’s replies as citations with stable cite keys (ba-). The board becomes referenceable as a tool. Only closed months answer — the current month is still being written.

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": {
      "month": "<month>"
    },
    "name": "board_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoOptional: cap on threads/replies returned (default 25, max 50)
monthYesYYYY-MM — a closed month (anything before this one)
authorNoOptional: exact member name — returns their replies in that month as citations

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false and openWorldHint=true, so the fact that a 'query' tool is not read-only is a meaningful signal the description should clarify. The line 'The board becomes referenceable as a tool' gestures at some side effect but is too vague to tell an agent what actually changes or why the call is not read-only. The cite-key format (ba-<id>) and the closed-month rule are useful additions beyond the annotations.

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?

Three compact sentences with the scope and result shape front-loaded. The middle sentence, 'The board becomes referenceable as a tool,' is cryptic and does not clearly earn its place given how little it conveys.

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?

For a 3-parameter tool with full schema coverage and no output schema, the description covers inputs and the general return shape (threads, citations, cite keys) adequately. What it leaves unresolved is the unexplained side effect implied by readOnlyHint=false and the cryptic 'referenceable as a tool' claim, which an agent cannot act on.

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 100%, so the schema already documents month format, limit defaults/max, and author behavior; baseline 3 applies. The description adds only the cite-key format and reiterates the closed-month restriction, which the schema already states. No new meaning is added for limit or author beyond the schema text.

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 ('Query a closed month of the board') plus the two result shapes: threads opened in that month, and with an author, that member's replies as citations. The closed-month scope further narrows it against siblings like board_list_threads. It does not explicitly name a sibling it is not, so it stops short of 5.

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?

Gives one hard usage constraint — only closed months answer, the current month is still being written — which is genuinely useful routing information. It also implies the author parameter switches modes. However, it never names an alternative tool (board_list_threads, board_read_thread, board_search) or states when this is preferable, so usage is implied rather than guided.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources