Skip to main content
Glama
Sign In
LemonMCP

LemonMCP

Official
by lemonXGroup
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

inspect_module

Fetch the active manifest, UI schema, and ESM sources for one installed Module by reverse-domain ID to inspect its implementation.

Instructions

Fetches the active manifest, UI schema, and ESM sources of one installed Module.

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

Input Schema

NameRequiredDescriptionDefault
module_idYesReverse-domain Module id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. 'Fetches' implies a read, but the description says nothing about permissions, whether the module must be installed/enabled, payload size, or error behavior when the module_id is unknown.

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?

A single efficient sentence with the resource and scope front-loaded; every word earns its place and there is no filler.

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?

With no output schema, the description usefully enumerates the three returned artifacts, which is the main thing an agent needs. The lack of annotations leaves permission and failure behavior unspecified, but for a one-param read tool this is close to complete.

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 coverage is 100% and module_id is documented as a reverse-domain id, so the schema already does the work. The description adds only the implication that the target must be an installed module, which is marginal added value.

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 ('Fetches') and enumerates exactly what is retrieved: active manifest, UI schema, and ESM sources of one installed Module. This meaningfully differentiates it from siblings like get_module_package or get_module_runtime_status, though it doesn't name those siblings directly.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as get_module_package. The agent must infer context from the sibling list on its own.

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

Deploy Server

Other Tools