Skip to main content
Glama
selvinchen97-lab

selvin-search-mcp

web_search

Searches the web to retrieve real-time information, returning summarized content and source count. Supports planning sessions for gated multi-step searches or one-shot mode for direct lookups.

Instructions

Performs a web search through the configured search mode and caches the source list.

PLANNING GATE: when `plan_session_id` is provided, this tool refuses to run until the
plan is complete (all required phases done, unverified_terms covered). If you intend to
skip planning (one-shot factual lookup), call this tool with an empty `plan_session_id`.

Returns:
  - session_id      string  pass to get_sources to retrieve full source list
  - content         string  answer from API-search summarization or online model search
  - sources_count   int
  - cached          bool    true if response was served from in-memory result cache
  - budget          object  (when plan_session_id set) actual vs estimated tool calls

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modelNoOptional model ID for this request only. This value is used ONLY when user explicitly provided.
queryYesClear, self-contained natural-language search query.
platformNoTarget platform to focus on (e.g., 'Twitter', 'GitHub', 'Reddit'). Leave empty for general web search.
plan_session_idNoPlanning session ID. When set, the tool enforces plan completion before running. Empty = no gating (one-shot mode).
Behavior5/5

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

Despite no annotations, the description thoroughly discloses caching behavior, planning gate enforcement, return fields, and cache-hit detection, covering all major behavioral traits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with clear sections, each sentence adds meaningful information without waste, and front-loaded with the core purpose.

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?

Given no output schema, describes return fields adequately. Covers planning integration, caching, and platform filtering, making it complete for a search tool in this context.

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 coverage is 100% so baseline 3. Description adds value by explaining the plan_session_id gating, platform focus, and model override context, going beyond schema descriptions.

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?

Clearly states it performs web search and caches results, distinguishing from sibling tools like get_sources which retrieves full source list.

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?

Explicitly describes the PLANNING GATE behavior and when to use empty plan_session_id for one-shot lookups, providing clear context for when this tool is appropriate vs alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/selvinchen97-lab/GLM-search-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server