mitbbs.ai

Search News

search_news

Read-only

Search mitbbs.ai Chinese-language news headlines and forum posts (guest-readable boards only). Returns url, title, excerpt, board, author, posted_at, source_name, source_url, rights_basis per result.

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": {
      "q": "<q>"
    },
    "name": "search_news"
  }
}

Input Schema

Name	Required	Description
`q`	Yes	Search keywords (Chinese or English)
`board`	No	Restrict to one forum id
`limit`	No

Output Schema

Name	Required	Description	Default
`ok`	No
`query`	No
`results`	No
`attribution`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 3, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is clear. The description adds that results are limited to guest-readable boards and lists returned fields, but it does not explain ranking, pagination, rate limits, or other search behavior 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences with the core purpose front-loaded and no wasted wording. The return-field list is compact and does not obscure the primary action.

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 simple search tool with annotations and an output schema, the description covers purpose, content domain, board scope, and expected result fields. It is not fully complete because it omits guidance on the limit parameter and does not mention how board ids relate to the list_boards sibling.

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 67%: q and board are documented, while limit is not described in the schema or description. The description adds domain context around Chinese-language news/forum content and guest-readable boards, which helps interpret board scope, but it does not clarify the limit parameter or explain how to obtain board ids.

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: search mitbbs.ai Chinese-language news headlines and forum posts. It also narrows scope to guest-readable boards, making the tool distinguishable from generic web search. It does not explicitly differentiate from siblings such as get_story or list_boards, so it falls short of a 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?

The description implies usage through the verb 'Search' and the content scope 'news headlines and forum posts.' The parenthetical 'guest-readable boards only' adds a constraint on where the search applies. However, it gives no explicit guidance on when to choose this tool over siblings like get_story or list_boards.

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

All mitbbs.ai tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?