Skip to main content
Glama

renef_module_symbols

Lists all symbols in a module, including non-exported ones, with optional filter and limit controls for targeted inspection.

Instructions

List all symbols (including non-exported) of a module. filter/limit as in renef_module_exports.

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": {
      "name": "<name>"
    },
    "name": "renef_module_symbols"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
limitNo
filterNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; 'List' does imply a read-only operation and it usefully discloses that the result set spans all symbols, not just the exported surface. It says nothing about default truncation (limit defaults to 200), ordering, or behavior when the module name is unknown, so the behavioral picture is only partial.

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?

Two short sentences with the scope-defining detail ('including non-exported') front-loaded; there is no filler. The cross-reference to another tool's parameter docs is compact but offloads work the reader still has to do.

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?

An output schema exists, so return values need not be explained, and the core purpose is clear enough to invoke. What remains missing is how filter and limit actually behave and whether results are capped, which matters for a listing tool with a silent default limit.

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?

Schema description coverage is 0% across all three parameters, so the description must compensate and largely does not: 'name' is only implied, and the filter/limit semantics are deferred to another tool's documentation rather than explained (substring vs regex, case sensitivity, truncation). Pointing at a sibling is not the same as documenting the parameters.

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?

States a specific verb and resource ('List all symbols ... of a module') and immediately scopes it by noting non-exported symbols are included, which is exactly what separates it from the sibling renef_module_exports. It stops short of naming that sibling as the alternative, but the distinction is still legible without opening a schema.

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

Usage Guidelines3/5

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

The inclusion of non-exported symbols implicitly signals when to prefer this over renef_module_exports, but the choice is never stated explicitly and no exclusions or prerequisites are given. The 'as in renef_module_exports' clause is guidance about parameters, not about when to call this tool.

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