Skip to main content
Glama

Search Any Topic

gt_search
Read-onlyIdempotent

Search for current best practices, documentation, and guidance on any topic without specifying a library name. Get authoritative results for web standards, security, accessibility, performance, APIs, and more.

Instructions

Search for latest best practices, docs, or guidance on ANY topic — no library name needed.

Current year: 2026. All searches are normalized to fetch 2026 content.

Works for:

  • Library best practices: "latest React patterns", "Next.js server actions"

  • Web standards: "CSS container queries", "WebSocket API", "Fetch API"

  • Security: "OWASP SQL injection prevention", "JWT security best practices", "CSP headers"

  • Accessibility: "WCAG 2.2 focus indicators", "ARIA roles reference"

  • Performance: "Core Web Vitals optimization", "LCP improvements"

  • APIs & protocols: "REST API design", "HTTP/3 vs HTTP/2", "OpenAPI 3.1"

  • Auth standards: "OAuth 2.1 PKCE", "WebAuthn passkeys", "OIDC"

  • Infrastructure: "Docker best practices", "GitHub Actions CI/CD"

  • Anything else: just ask

If the query names ONE specific library, prefer gt_resolve_library + gt_get_docs/gt_best_practices for version-accurate, registry-backed results — use gt_search for standards, cross-cutting topics, or when no library applies. For browser/runtime feature support use gt_compat; for GitHub code examples use gt_examples.

Say "use gt" or "gt search [topic]" to invoke.

Examples:

  • gt_search({ query: "latest best practices" }) — auto-detects from project context

  • gt_search({ query: "WCAG 2.2 keyboard navigation" })

  • gt_search({ query: "SQL injection prevention 2026" })

  • gt_search({ query: "CSS container queries browser support" })

  • gt_search({ query: "React Server Components patterns" })

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesWhat you want to know. Can be anything: 'latest React best practices', 'WCAG 2.2 focus indicators', 'OWASP SQL injection prevention', 'CSS container queries browser support', 'JWT security', 'HTTP/3 vs HTTP/2', 'Web Workers API'. No library name required.
tokensNoMax tokens to return (default: 8000, max: 20000)
Behavior4/5

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

Annotations already provide read-only, open-world, idempotent hints. Description adds context: year normalization, auto-detection from project context, and token constraints. No contradictions.

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?

Well-structured with bullet points and headings. Front-loaded with main purpose. Slightly long but every sentence adds value. Could be tightened slightly, but highly functional.

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?

Rich description covers purpose, usage guidelines, parameters with examples, and behavioral context. No output schema but annotations and schema cover remaining needs. Complete for a search tool with many use cases.

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% with detailed descriptions for both 'query' and 'tokens'. Description reinforces 'query' with many examples but does not add new meaning beyond schema. Baseline 3 appropriate.

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?

Description uses 'Search for latest best practices, docs, or guidance on ANY topic' with specific verb 'Search' and resource 'any topic'. It distinguishes from siblings by naming alternative tools for specific library queries.

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 states when to use gt_search vs alternatives: 'If the query names ONE specific library, prefer gt_resolve_library + gt_get_docs/gt_best_practices...' and also mentions gt_compat and gt_examples. Clear context with examples.

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/rm-rf-prod/ws-mcp'

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