Skip to main content
Glama
yuanbao-search-mcp

yuanbao-search-mcp

by GtJerry111

Search the general web

yuanbao_search_web
Read-only

Search the general web via Yuanbao and filter results by source scope, relevance or date, and recent publication window to find relevant pages.

Instructions

Search the general web through Yuanbao.

Args: query: Keywords to search. limit: Maximum results, 1-20. Defaults to the server-configured limit. scope: "all", "gov", or "media". sort: "relevance" (default) or "date" (newest first; undated last). days: Optional local filter for results published in the last N days.

Returns: Results with title, URL, source, date, snippet, date_unknown flags, related search queries, and warnings. Does not support site: or Boolean operators.

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": {
      "query": "<query>"
    },
    "name": "yuanbao_search_web"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
sortNorelevance
limitNo
queryYes
scopeNoall

Output Schema

NameRequiredDescriptionDefault
countYes
queryYes
scopeYes
resultsNo
warningsNo
related_queriesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, openWorld, non-idempotent, non-destructive), and the description adds real behavioral detail: the return fields including date_unknown flags and warnings, the fact that site: and Boolean syntax are unsupported, that days is a post-hoc local filter, and that date-sorted results put undated items last. It does not discuss rate limits, result-count capping between search and the local filter, or auth, leaving some room above a 4.

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 Args/Returns structure is front-loaded and easy to scan, with no filler prose. The Returns block partially duplicates the existing output schema, though the notes on date_unknown and warnings still earn their place.

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 five-parameter search tool with an output schema, this is close to complete: parameters, return shape, and query-syntax limitations are all addressed. The remaining gap is that the scope values and the limit-default discrepancy are unexplained, which an agent invoking the tool would want resolved.

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 0%, so the description carries the full burden. It documents all five parameters, but most entries merely restate the schema: the scope and sort enum values are copied verbatim with no explanation of what "gov" or "media" actually restrict, and limit says "defaults to the server-configured limit" while the schema declares default 10, a minor mismatch. Only "days is a local filter" and "undated last" add genuine semantic value beyond the structured fields.

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 gives a clear verb+resource ("Search the general web") and the phrase "general web" implicitly separates it from the academic and WeChat-article siblings. It stops short of explicitly naming those alternatives, so the contrast is inferable but not stated.

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?

Usage is implied by "general web" and the scope enum, and the note about unsupported site:/Boolean operators is a useful boundary. However, there is no explicit when-to-use guidance versus yuanbao_search_academic or the WeChat tools, and no statement of when-not to use this tool.

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