Skip to main content
Glama
Sign In

Profullstack

by com.profullstack
OverviewDiscussionsAdmin

HQTUI BBS: Board overview

hqtui_bbs_board_overview
Read-onlyIdempotent

[HQTUI BBS] What this board is: its name, tagline, size, and the forums the current token may see. Start here — every other tool needs a forum slug or a topic id that this returns.

Served by HQTUI BBS (https://bbs.hqtui.com/docs/mcp).

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": "hqtui_bbs_board_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorldHint, so the safety profile is covered. The description adds genuinely new behavior: results are permission-scoped to "the forums the current token may see," which explains why output can differ per caller.

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?

Content is front-loaded: what it returns, then why to call it first. The trailing "Served by HQTUI BBS (URL)" line is boilerplate that does not help selection, which keeps it from a 5.

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 carries the burden of describing the return payload, and it does so at a field level. The minor gap is that it claims to return topic ids while only promising visible forums, leaving the exact shape slightly ambiguous.

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

Parameters4/5

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

The tool takes zero parameters, so the baseline is 4 and there is no parameter semantics to document. The description correctly implies the call needs no input.

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?

Names the resource and enumerates the specific fields returned (name, tagline, size, visible forums), which lets an agent distinguish it from list_forums/list_topics without opening schemas. It stops short of explicitly contrasting with hqtui_bbs_list_forums, whose content partially overlaps.

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?

"Start here — every other tool needs a forum slug or a topic id that this returns" gives a clear entry-point rule and the reason for it. No explicit when-not is needed for a zero-parameter overview tool, so the guidance is essentially complete.

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

All Profullstack toolsInspect
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