gmod-mcp

inspect_entity

Inspect a Garry's Mod entity by index to retrieve its class, model, health, owner, and key-value pairs.

Instructions

Details of one entity by index: class, model, health, owner, key-values.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "index": "<index>"
    },
    "name": "inspect_entity"
  }
}

Input Schema

Name	Required	Description	Default
`index`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.0Jul 29, 2026

TDQS

C2.7/5.0

Behavior2/5

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

Annotations lack readOnlyHint or destructiveHint. Description does not disclose what happens if index is out of bounds, whether it's a read-only operation, or any side effects. For a tool with minimal annotation coverage, more behavioral context is needed.

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?

Single sentence, front-loaded with the key action and resource. No redundancy, but could be slightly more structured with bullet points for listed fields.

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

Completeness2/5

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

No output schema, so description should explain return format. It lists fields but doesn't specify structure or types. Missing details on how key-values are represented, or whether all fields are always present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Description only mentions 'by index' for the single parameter 'index'. Schema has 0% description coverage, so description should add meaning, but it merely restates the parameter's purpose without additional semantics like range or format.

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?

Description clearly states it provides details of one entity by index, listing specific fields (class, model, health, owner, key-values). Distinguished from siblings like read_entities which likely list all entities.

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 on when to use this tool versus alternatives such as read_entities. No prerequisites or context provided.

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