gmod-mcp

read_hooks

Retrieve registered Garry's Mod hooks, filter by event, and get event-to-identifier mappings for addon development.

Instructions

Registered hooks (hook.GetTable), filterable by event. Returns event -> identifiers.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "read_hooks"
  }
}

Input Schema

Name	Required	Description	Default
`event`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.0Jul 29, 2026

TDQS

B3.2/5.0

Behavior2/5

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

The description mentions the internal function 'hook.GetTable' and that it returns a mapping, but does not disclose behavioral traits such as read-only nature, required permissions, or side effects. With no annotations beyond title, the description fails to fully inform the agent about safe and expected usage.

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?

The description is extremely concise with two short sentences. It is front-loaded with the main purpose and contains no unnecessary words. Every part contributes value.

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 simple tool with one optional parameter and no output schema, the description adequately covers the core functionality and return format. However, it could be more robust by mentioning error conditions or data format details to fully complete the context.

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?

The description indicates the 'event' parameter can be used for filtering, adding meaning beyond the schema (which has no description). However, it does not specify valid values, format, or optionality, leaving gaps. Given 0% schema coverage, this is moderate compensation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool reads registered hooks and returns a mapping from event to identifiers, indicating a specific verb and resource. However, it does not differentiate from sibling tools like 'read_entities' or 'read_convars', leaving some ambiguity about when to use this specific tool.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives, when not to use it, or any prerequisites. The description lacks explicit context for selecting this tool among many read-type siblings.

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