Skip to main content
Glama
WaterSippin

OSRS MCP Server

Official
by WaterSippin

search_spritetypes

Search sprite image definitions in the spritetypes.txt file for OSRS interface design. Input a query, page number, and page size to retrieve specific sprite data efficiently.

Instructions

Search the spritetypes.txt file for sprite image definitions used in the interface.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination
pageSizeNoNumber of results per page
queryYesThe term to search for in the file

Implementation Reference

  • Handler code executed when 'search_spritetypes' is called. Parses input arguments, determines the spritetypes.txt file path, checks if file exists, searches the file using the shared searchFile helper, and returns paginated results.
    const fileSearchArgs = getSchemaForTool(name).parse(args) as { query: string; page?: number; pageSize?: number };
    const { query, page: filePage = 1, pageSize: filePageSize = 10 } = fileSearchArgs;
    const filename = `${name.replace('search_', '')}.txt`;
    const filePath = path.join(getDataDir(), filename);
    
    if (!fileExists(filename)) {
        return responseToString({ error: `${filename} not found in data directory` });
    }
    
    const fileResults = await searchFile(filePath, query, filePage, filePageSize);
    return responseToString(fileResults);
  • Zod schema definition used for input validation of search_spritetypes tool (shared with other search_* tools). Defines query, pagination parameters.
    const FileSearchSchema = z.object({
        query: z.string().describe("The term to search for in the file"),
        page: z.number().int().min(1).optional().default(1).describe("Page number for pagination"),
        pageSize: z.number().int().min(1).max(100).optional().default(10).describe("Number of results per page")
    });
  • Logic in getSchemaForTool function that selects FileSearchSchema for any tool name starting with 'search_', including search_spritetypes.
            if (toolName.startsWith("search_")) {
                return FileSearchSchema;
            }
            throw new Error(`Unknown tool: ${toolName}`);
    }
  • index.ts:358-360 (registration)
    Tool registration/declaration in getToolDefinitions() array, providing name and description returned by listTools.
        name: "search_spritetypes",
        description: "Search the spritetypes.txt file for sprite image definitions used in the interface.",
    },
  • Core helper function that performs the actual file search: reads lines, matches query (case-insensitive, spaces to underscores), paginates results, formats as ID-value pairs, returns structured results with pagination info. Called by all search_* handlers including search_spritetypes.
    async function searchFile(filePath: string, searchTerm: string, page: number = 1, pageSize: number = 10): Promise<any> {
        //replace spaces with underscores
        searchTerm = searchTerm.replace(" ", "_");
        return new Promise((resolve, reject) => {
            if (!fs.existsSync(filePath)) {
                reject(new Error(`File not found: ${filePath}`));
                return;
            }
    
            const results: {line: string, lineNumber: number}[] = [];
            const fileStream = fs.createReadStream(filePath);
            const rl = readline.createInterface({
                input: fileStream,
                crlfDelay: Infinity
            });
    
            let lineNumber = 0;
            
            rl.on('line', (line) => {
                lineNumber++;
                if (line.toLowerCase().includes(searchTerm.toLowerCase())) {
                    results.push({ line, lineNumber });
                }
            });
    
            rl.on('close', () => {
                const totalResults = results.length;
                const totalPages = Math.ceil(totalResults / pageSize);
                const startIndex = (page - 1) * pageSize;
                const endIndex = startIndex + pageSize;
                const paginatedResults = results.slice(startIndex, endIndex);
    
                // Process the results to extract key-value pairs if possible
                const formattedResults = paginatedResults.map(result => {
                    // Try to format as key-value pair (common for ID data files)
                    const parts = result.line.split(/\s+/);
                    if (parts.length >= 2) {
                        const id = parts[0];
                        const value = parts.slice(1).join(' ');
                        return {
                            ...result,
                            id,
                            value,
                            formatted: `${id}\t${value}`
                        };
                    }
                    return result;
                });
    
                resolve({
                    results: formattedResults,
                    pagination: {
                        page,
                        pageSize,
                        totalResults,
                        totalPages,
                        hasNextPage: page < totalPages,
                        hasPreviousPage: page > 1
                    }
                });
            });
    
            rl.on('error', (err) => {
                reject(err);
            });
        });
    }

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/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 burden. It mentions searching a file but doesn't disclose behavioral traits like read-only vs. destructive operations, authentication needs, rate limits, or error handling. This is inadequate for a tool with no 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, efficient sentence that front-loads key information (search action and resource). There is no wasted text, making it highly concise and well-structured.

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 no annotations and no output schema, the description is incomplete. It doesn't explain what the search returns (e.g., list of definitions, metadata), error conditions, or how results are formatted, leaving significant gaps for agent understanding.

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 fully documents parameters (query, page, pageSize). The description adds no additional meaning beyond implying a search term is used, aligning with the baseline score when schema does the heavy lifting.

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 ('search') and resource ('spritetypes.txt file for sprite image definitions'), making the purpose understandable. It doesn't explicitly differentiate from sibling tools like 'search_data_file' or 'search_iftypes', which might have overlapping domains, so it misses the highest score.

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?

No guidance is provided on when to use this tool versus alternatives. With many sibling search tools (e.g., search_data_file, search_iftypes), the description lacks context on specific use cases, prerequisites, or exclusions, leaving the agent to infer usage.

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