Skip to main content
Glama

Search Any Topic

gt_search
Read-onlyIdempotent

Search for best practices, documentation, and guidance on any topic. Get authoritative results normalized to 2026 content without needing a library name.

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

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 indicate read-only and idempotent behavior. The description adds useful context: searches are normalized to 2026 content and auto-detect project context. This goes beyond annotations but does not cover all behavioral aspects like output format.

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 description is well-structured with a clear main statement, bullet list, and examples. It is longer than average but the examples are helpful for a broad tool. No redundancy, but could be slightly more concise.

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

Completeness3/5

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

The description covers usage intent well but lacks output format details (e.g., what the search returns). Given no output schema, this is a gap. Annotations provide safety profile, so overall adequate but incomplete.

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 coverage is 100% with good descriptions for both query and tokens. The description provides examples but does not add new semantic meaning beyond the schema. Baseline 3 is 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?

The description clearly states the verb 'search' and resource 'ANY topic', and distinguishes from specialized sibling tools like gt_best_practices by emphasizing no library name needed. Examples cover a wide range of topics, reinforcing the general-purpose nature.

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?

The description explicitly lists use cases and provides invocation instructions. It does not explicitly state when not to use or alternatives, but the broad scope and 'Works for' section imply a general-purpose role, leaving some ambiguity for sibling differentiation.

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