Skip to main content
Glama

get_module_context

Get an overview of all symbols in a directory to understand package structure before drilling into specific files.

Instructions

Get an overview of all symbols in a directory/package.

This is the intermediate zoom level between get_project_skeleton (whole project) and get_file_context (single file). Use it to understand what a package contains before drilling into specifics.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
module_pathNoDirectory path relative to project root (e.g. "services", "grafyx/graph"). Empty string means the whole project.
detailNoLevel of detail: "signatures", "summary" (default), or "full".summary
include_hintsNoIf True, append navigation suggestions.
offsetNoNumber of files to skip (for paginating large modules).
limitNoMaximum number of files to return (0 = no limit, default). Combine with offset to page through modules with hundreds of files where the response would otherwise be truncated. ``total_files`` in the response always reflects the full count, regardless of pagination.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does not disclose behavioral traits like side effects, auth needs, or rate limits. However, the read-only nature is implied by 'Get an overview' and no destructive actions are suggested.

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 two sentences, front-loaded with the primary purpose, and every sentence adds value. No wasted words.

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

Completeness5/5

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

Given that an output schema exists, the description need not explain return values. It provides the zoom level context, usage guidance, and all parameters are documented in the schema. The description is complete for its purpose.

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 100%, so the schema already documents all parameters. The tool description does not add additional meaning beyond what is in the schema parameters' descriptions.

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

Purpose5/5

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

The description clearly states the tool's purpose: 'Get an overview of all symbols in a directory/package.' It distinguishes itself from siblings by specifying it's the intermediate zoom level between get_project_skeleton and get_file_context.

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

Usage Guidelines5/5

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

The description explicitly says: 'Use it to understand what a package contains before drilling into specifics.' This implies when to use (intermediate analysis) and when not (use siblings for whole project or single file).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bilal07karadeniz/Grafyx'

If you have feedback or need assistance with the MCP directory API, please join our Discord server