Skip to main content
Glama
WaterSippin

OSRS MCP Server

Official
by WaterSippin

get_file_details

Retrieve detailed information about a specific file in the OSRS data directory using the filename. Designed for accessing game data definitions via the OSRS MCP Server.

Instructions

Get details about a file in the data directory.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filenameYesThe filename to get details for in the data directory

Implementation Reference

  • The main handler function that executes the get_file_details tool logic, retrieving file existence, size, line count, and timestamps from the data directory.
    async function getFileDetails(filename: string): Promise<any> {
        try {
            const filePath = path.join(getDataDir(), filename);
            if (!fs.existsSync(filePath)) {
                return { exists: false };
            }
    
            const stats = await fs.promises.stat(filePath);
            const lineCount = await getFileLineCount(filePath);
    
            return {
                exists: true,
                size: stats.size,
                lineCount,
                created: stats.birthtime,
                lastModified: stats.mtime
            };
        } catch (error) {
            console.error(`Error getting file details for ${filename}:`, error);
            return { exists: false, error: 'Error getting file details' };
        }
    }
  • Zod schema defining the input validation for the get_file_details tool (filename parameter).
    const FileDetailsSchema = z.object({
        filename: z.string().describe("The filename to get details for in the data directory")
    });
  • index.ts:370-372 (registration)
    Tool registration in the getToolDefinitions() function, listing get_file_details as an available tool.
        name: "get_file_details",
        description: "Get details about a file in the data directory.",
    },
  • index.ts:473-483 (registration)
    Registration and dispatching logic in the main CallToolRequestSchema handler switch, validating arguments and invoking the getFileDetails handler.
    case "get_file_details":
        const detailsArgs = getSchemaForTool(name).parse(args) as { filename: string };
        const { filename: detailsFilename } = detailsArgs;
        
        // Security check to prevent directory traversal
        if (detailsFilename.includes('..') || detailsFilename.includes('/') || detailsFilename.includes('\\')) {
            throw new Error('Invalid filename');
        }
        
        const details = await getFileDetails(detailsFilename);
        return responseToString(details);
  • Helper function used by getFileDetails to count the number of lines in a file efficiently using streams.
    async function getFileLineCount(filePath: string): Promise<number> {
        return new Promise((resolve, reject) => {
            let lineCount = 0;
            const stream = fs.createReadStream(filePath);
            stream.on('data', (chunk) => {
                for (let i = 0; i < chunk.length; i++) {
                    if (chunk[i] === 10) { // ASCII code for newline
                        lineCount++;
                    }
                }
            });
            stream.on('end', () => resolve(lineCount));
            stream.on('error', reject);
        });
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool retrieves details but doesn't specify what details are returned (e.g., metadata, size, permissions), whether it's read-only (implied but not explicit), or any error conditions (e.g., file not found). This is inadequate for a tool with zero annotation coverage.

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 a single, direct sentence with no wasted words. It front-loads the core purpose efficiently, making it easy to parse and understand quickly.

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?

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what 'details' include, potential errors, or behavioral traits, leaving significant gaps for a tool that likely returns structured data. More context is needed to fully inform the agent.

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?

The schema description coverage is 100%, with the 'filename' parameter fully documented in the schema. The description adds no additional meaning beyond implying the file must exist in the 'data directory', which is already covered by the schema's description. This meets the baseline for high schema coverage.

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?

The description clearly states the action ('Get details') and resource ('about a file in the data directory'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'list_data_files' (which likely lists files) or 'search_data_file' (which likely searches file contents), missing the opportunity to clarify its specific scope.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an existing filename), exclusions, or comparisons to siblings like 'search_data_file' for finding files by content. This leaves the agent without context for tool selection.

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

Related 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/WaterSippin/mcp-osrs'

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