Skip to main content
Glama

Search GLua Community & GitHub

web_search_glua
Read-onlyIdempotent

Search Garry's Mod community forums, GitHub, Reddit, and Steam for solutions to obscure bugs, workarounds, and undocumented engine behaviors. Filters by platform and limits results for targeted troubleshooting.

Instructions

Search external Garry's Mod developer communities, GitHub repositories, Facepunch archives, Reddit, and Steam Community forums for community-developed solutions, workarounds, and undocumented engine behaviors. Read-only external web search with open-world egress; requires no credentials and produces zero local file mutations or state modifications. Requires a query string. Optionally filter target domains with domain_filter ('github', 'facepunch', 'reddit', 'steam', 'all', default 'all') and limit results with max_results (1 to 10, default 5). Use this tool for troubleshooting obscure runtime bugs, researching community conventions, finding GitHub code implementations, or resolving undocumented engine quirks where official documentation is silent. Do NOT use for official Garry's Mod API reference, hook signatures, or standard library documentation (use get_gmod_symbol for exact lookups or search_gmod_wiki for topic searches). Returns a GModToolResult envelope with status ('success' or 'failed'), summary, and data containing query and results array (title, destination url, snippet, source platform).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query targeting Garry's Mod developer topics, error messages, or code patterns (e.g. 'GM:SetupMove prediction stutter', 'DarkRP custom job HUD').
max_resultsNoMaximum number of community search results to return (integer between 1 and 10, default is 5).
domain_filterNoRestricts search results to specific developer community platforms ('github', 'facepunch', 'reddit', 'steam', or 'all').all

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesDomain-specific typed payload returned by the tool.
statusYesExecution status of the tool call ('success', 'partial', 'blocked', or 'failed').
summaryYesConcise, human-readable summary of operational findings, diagnostics, or execution outcome.
evidenceYesTraceability evidence including cited documentation and generated artifacts.
warningsYesList of non-fatal warnings, lint advisories, engine caveats, or security notices.
nextActionsNoActionable, ordered recommendations for the agent's immediate next steps.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / domain_filter / description
      Previous value: -"Target community platform"New value: +"Restricts search results to specific developer community platforms ('github', 'facepunch', 'reddit', 'steam', or 'all')."
    • changedInput schema / properties / max_results / description
      Previous value: -"Max results"New value: +"Maximum number of community search results to return (integer between 1 and 10, default is 5)."
    • changedInput schema / properties / query / description
      Previous value: -"Target query"New value: +"Search query targeting Garry's Mod developer topics, error messages, or code patterns (e.g. 'GM:SetupMove prediction stutter', 'DarkRP custom job HUD')."
    • addedInput schema / properties / query / minLength
      Added value: +1
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "data": {
      +      "description": "Domain-specific typed payload returned by the tool.",
      +      "properties": {
      +        "query": {
      +          "description": "The community search query executed.",
      +          "type": "string"
      +        },
      +        "results": {
      +          "description": "Community forum, GitHub, and workshop search results with relevant code snippets.",
      +          "items": {
      +            "properties": {
      +              "snippet": {
      +                "description": "Relevant code excerpt, error explanation, or discussion snippet.",
      +                "type": "string"
      +              },
      +              "source": {
      +                "description": "Source platform ('github', 'facepunch', 'reddit', 'steam', or 'web').",
      +                "type": "string"
      +              },
      +              "title": {
      +                "description": "Post, thread, or repository title.",
      +                "type": "string"
      +              },
      +              "url": {
      +                "description": "Destination link.",
      +                "type": "string"
      +              }
      +            },
      +            "required": [
      +              "title",
      +              "url",
      +              "snippet",
      +              "source"
      +            ],
      +            "type": "object"
      +          },
      +          "type": "array"
      +        }
      +      },
      +      "required": [
      +        "query",
      +        "results"
      +      ],
      +      "type": "object"
      +    },
      +    "evidence": {
      +      "description": "Traceability evidence including cited documentation and generated artifacts.",
      +      "properties": {
      +        "artifacts": {
      +          "description": "Files, packages, or manifests generated on disk or in memory.",
      +          "items": {
      +            "properties": {
      +              "label": {
      +                "description": "Descriptive label of the generated artifact.",
      +                "type": "string"
      +              },
      +              "sha256": {
      +                "description": "SHA-256 hash of the generated file.",
      +                "type": "string"
      +              },
      +              "uri": {
      +                "description": "File path or URI of the generated artifact.",
      +                "type": "string"
      +              }
      +            },
      +            "required": [
      +              "label",
      +              "uri"
      +            ],
      +            "type": "object"
      +          },
      +          "type": "array"
      +        },
      +        "inputsDigest": {
      +          "description": "SHA-256 digest of normalized tool inputs for auditability.",
      +          "type": "string"
      +        },
      +        "sources": {
      +          "description": "Cited documentation, wiki pages, or external web sources supporting the result.",
      +          "items": {
      +            "properties": {
      +              "label": {
      +                "description": "Display name or title of the cited resource.",
      +                "type": "string"
      +              },
      +              "retrievedAt": {
      +                "description": "ISO-8601 timestamp of source retrieval.",
      +                "type": "string"
      +              },
      +              "uri": {
      +                "description": "Canonical URI or URL of the documentation or source.",
      +                "type": "string"
      +              }
      +            },
      +            "required": [
      +              "label"
      +            ],
      +            "type": "object"
      +          },
      +          "type": "array"
      +        }
      +      },
      +      "required": [
      +        "sources",
      +        "artifacts"
      +      ],
      +      "type": "object"
      +    },
      +    "nextActions": {
      +      "description": "Actionable, ordered recommendations for the agent's immediate next steps.",
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "status": {
      +      "description": "Execution status of the tool call ('success', 'partial', 'blocked', or 'failed').",
      +      "enum": [
      +        "success",
      +        "partial",
      +        "blocked",
      +        "failed"
      +      ],
      +      "type": "string"
      +    },
      +    "summary": {
      +      "description": "Concise, human-readable summary of operational findings, diagnostics, or execution outcome.",
      +      "type": "string"
      +    },
      +    "warnings": {
      +      "description": "List of non-fatal warnings, lint advisories, engine caveats, or security notices.",
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "status",
      +    "summary",
      +    "data",
      +    "warnings",
      +    "evidence"
      +  ],
      +  "type": "object"
      +}
  2. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds useful behavioral context beyond those: 'requires no credentials and produces zero local file mutations or state modifications,' plus the exact return envelope with success/failed status. No contradiction exists.

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 front-loaded with the core purpose, followed by usage guidance, exclusions, and return format. It is slightly redundant with annotations and the output schema, but every sentence earns its place and the overall structure is easy to scan.

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?

For a read-only external search tool with robust annotations, full parameter schema coverage, and an output schema, the description is complete. It covers purpose, invocation requirements, optional parameters, when to use and avoid the tool, alternative tools, and the result envelope shape, leaving no meaningful gap for an agent to call it correctly.

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%, and the schema already defines query, max_results, and domain_filter with defaults and constraints. The description recaps these parameter names and defaults but adds little new semantic meaning beyond what the schema provides, so 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 states a specific verb and resource: 'Search external Garry's Mod developer communities, GitHub repositories, Facepunch archives, Reddit, and Steam Community forums.' It also differentiates from siblings by explicitly saying it is not for official API reference, hook signatures, or standard library documentation, directing those cases to get_gmod_symbol and search_gmod_wiki.

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?

It explicitly lists when to use the tool: troubleshooting obscure runtime bugs, researching community conventions, finding GitHub code implementations, and resolving undocumented engine quirks. It also gives clear negative guidance with named alternatives, so an agent can confidently choose between web_search_glua and the official-doc tools.

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