Skip to main content
Glama

renef_module_exports

Lists exported symbols of a module, with optional substring filtering and an output limit, to help inspect module exports.

Instructions

List exported symbols of a module. Use filter to substring-match names, limit to cap output.

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_exports"
  }
}

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.4/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden and does disclose that output is capped via limit (default behavior implied by 200 in schema), which is useful. It says nothing about error behavior for an unknown module name, ordering of results, or whether limit truncates silently, which matters for a call with a default cap.

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, front-loaded with the purpose before the parameter hints; no filler. It is arguably too terse rather than padded, which is a completeness problem rather than a verbosity one.

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 described, and the tool is simple. However, for a 0%-coverage schema with a required module identifier, the description should at least confirm what 'name' refers to and what happens when filtering matches nothing.

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 0%, so the description needs to compensate; it adds real meaning for 'filter' (substring match) and 'limit' (caps output). The required 'name' parameter is never explained beyond the implicit 'of a module', leaving the most important argument to inference.

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 concrete verb and resource: 'List exported symbols of a module.' That is enough to distinguish it from generic symbol listings, but it never contrasts with the closely named sibling renef_module_symbols, so an agent cannot tell exports-only from all-symbols from the text alone.

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 description only explains how to steer the two optional parameters ('use filter to substring-match names, limit to cap output'); it gives no when-to-use context, no prerequisites (e.g. module must be attached/loaded), and no guidance on choosing this over renef_module_symbols.

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