Skip to main content
Glama

Chinng AI-Agent Portal

portal_search

BM25 full-text search over items (no body returned, token-light).

Ranked by weighted BM25 (SQLite FTS5) over the title, the original-language summary, the English summary, sentence-free English search signals and — for items whose license permits redistribution — the body. Japanese text is morphologically segmented at index time, so Japanese queries match words that a substring search would miss. Results carry score (0-1), rank and a snippet of the matching passage. Use portal_get to read a matched item's body.

Args: q: keyword(s). space-separated terms are ANDed. e.g. "openai gpt" category: category prefix match. e.g. "news" or "security" status: filter by ingested/processed/enriched/published (all if omitted) source: feed identifier. e.g. "ghost-chinng-lab" lang: original language. e.g. "ja" limit: number of results (default 20, max 100) offset: paging start position mode: "bm25" (default, relevance-ranked) or "index" (substring match, newest first)

Returns: {total, count, limit, offset, query, mode, total_is_capped, items[]} — same license-gated item shape as portal_list (summary/summary_en and snippet omitted for link-only, omission reason and search signals retained), never the body. In bm25 mode each item adds score / rank / snippet, and total is an estimate capped for cost. If the BM25 index is not usable the call transparently falls back to mode "index" and reports why in degraded_reason.

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

Input Schema

NameRequiredDescriptionDefault
qYes
langNo
modeNobm25
limitNo
offsetNo
sourceNo
statusNo
categoryNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/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 so: it discloses the license gating and field omission rules, that the body is never returned, that totals are estimates capped for cost, that Japanese is morphologically indexed, and that BM25 failure transparently degrades to index mode with a degraded_reason. This is exactly the kind of behavioral context annotations would otherwise need to supply.

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?

The critical constraint (no body, token-light) is front-loaded, and the Args/Returns blocks make it scannable despite its length. A few passages, such as the parenthetical list of BM25 signal fields, are denser than an agent strictly needs, but nothing is padding.

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

Completeness5/5

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

For an 8-parameter search tool with an output schema, the definition covers input semantics, return shape, degradation behavior, and license-gated omission rules. An agent has everything required to call it correctly and to interpret a degraded or partial response.

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

Parameters5/5

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

Schema description coverage is 0% across 8 parameters, so the description must compensate, and it does for every one: q term-ANDing with an example, category prefix-match with examples, the four status values, source as a feed identifier, lang, limit default/max, offset paging, and the two mode values. Only offset lacks an example, which is negligible.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening line gives a specific mechanism and resource (BM25 full-text search over items) plus an explicit scope limit (no body returned, token-light). It is immediately distinguishable from portal_get (body retrieval) and portal_list, and the ranking fields used are named concretely.

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?

It explicitly routes body-reading to portal_get and explains when each mode applies (bm25 relevance-ranked vs index substring/newest-first). What is missing is explicit guidance on when to choose this over portal_list, portal_popular, or portal_changes for browsing-type queries, so the routing is clear but not complete.

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