Skip to main content
Glama

web_search

Searches the web and returns summarized results with titles, snippets, and links, helping users find real-time news, technical documentation, tutorials, product details, and general knowledge.

Instructions

在互联网上搜索信息,返回相关搜索结果摘要 示例:web_search(query="Python最新版本", num_results=3)

适用场景:

  • 查询实时新闻、最新资讯

  • 搜索技术文档、教程

  • 获取生活常识、百科信息

  • 查找产品信息、价格对比

不适用场景:

  • 需要精确计算的问题(请使用计算器工具)

  • 查询当前天气(请使用天气工具)

Args: query: 搜索关键词,支持中英文 num_results: 返回结果数量,范围 1-10,默认 5

Returns: 搜索结果摘要,包含标题、摘要和链接

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

Input Schema

NameRequiredDescriptionDefault
queryYes
num_resultsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/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 disclose the return shape (title, summary, link), language support, and the num_results range/default. It omits operational traits such as rate limits, result freshness/caching, and failure behavior, which keeps it short of a 5.

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?

Purpose, example, use cases, exclusions, then Args/Returns — a clean front-loaded structure where each section is one line. The Args block partially restates schema fields, but it adds the 1-10 range, so the redundancy mostly earns its 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 two-parameter read tool with an output schema, the description covers invocation intent, parameter bounds, and return contents adequately. Residual gaps (pagination, ranking/freshness behavior) are minor given the tool's simplicity.

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?

Schema description coverage is 0%, so the description must compensate, and it does: query is documented as accepting Chinese and English keywords, and num_results is bounded to 1-10 with a default of 5 — the range is absent from the schema. Only the meaning of result relevance/ranking is left unexplained.

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 states a specific verb and resource (search the internet, return relevant result summaries) and the example call makes the operation concrete. The 不适用场景 section explicitly names calculator and weather siblings, so an agent can route correctly without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Both when-to-use (real-time news, technical docs, general knowledge, product/pricing) and when-not-to-use (precise computation → calculator, current weather → weather tool) are spelled out with named alternatives. Nothing about selection is left to inference.

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

Deploy Server

Other Tools