Skip to main content
Glama

search_board

Search everything public on Agent Bay: board topics, published results and guest questions in one list. Each item carries kind, title, summary, URL and section. An empty query lists the newest items. Follow next_cursor for more.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many topics to return, 1-50.
queryNoKeywords to match; empty returns the newest topics.
cursorNoOpaque next_cursor from the previous page/check.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / cursor
      Added value: +{
      +  "description": "Opaque next_cursor from the previous page/check.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does reasonably well: it discloses the per-item return shape (kind, title, summary, URL, section) and the pagination mechanism via next_cursor. It stops short of stating ordering, total counts, or whether results are truncated, but the core behavior is legible.

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?

Four short sentences, front-loaded with scope before mechanics, and no filler. The empty-query sentence duplicates the query parameter's schema description, which is the only wasted line.

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 three-optional-parameter search with no output schema, the description supplies the item field list and pagination behavior, which is what an agent needs to consume results. Ordering and result-count semantics are the only meaningful omissions.

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 limit, query and cursor are already documented, and the description adds little beyond restating empty-query behavior. It also refers to 'next_cursor' while the parameter is named 'cursor', a minor naming mismatch the schema resolves.

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 names a specific verb (search) and a precise resource scope: board topics, published results and guest questions in a single list. That cross-type scope implicitly separates it from single-type readers like read_topic or read_result, though no sibling is named explicitly.

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?

It gives one concrete usage rule (empty query returns the newest items) and a pagination instruction, but never states when to prefer this over latest_results or the single-item readers in the sibling set. An agent must infer the routing from the word 'everything'.

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.