Skip to main content
Glama
WaterSippin

OSRS MCP Server

Official
by WaterSippin

search_objtypes

Search object and item definitions in the OSRS game data by querying the objtypes.txt file. Supports pagination to browse results efficiently.

Instructions

Search the objtypes.txt file for object/item definitions in the game.

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 logic for 'search_objtypes' and similar tools. Parses arguments, constructs filepath to 'objtypes.txt', checks existence, calls searchFile, and returns paginated results.
    case "search_varptypes":
    case "search_varbittypes":
    case "search_iftypes":
    case "search_invtypes":
    case "search_loctypes":
    case "search_npctypes":
    case "search_objtypes":
    case "search_rowtypes":
    case "search_seqtypes":
    case "search_soundtypes":
    case "search_spottypes":
    case "search_spritetypes":
    case "search_tabletypes":
        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);
  • Input schema (FileSearchSchema) used for validating parameters of search_objtypes and other search_* tools.
    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")
    });
  • index.ts:338-340 (registration)
    Registration of the 'search_objtypes' tool in the list of available tools returned by ListTools.
        name: "search_objtypes",
        description: "Search the objtypes.txt file for object/item definitions in the game.",
    },
  • Core searchFile helper function that reads the file line-by-line, matches query (case-insensitive, spaces to underscores), paginates results, and formats as ID-value pairs.
    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);
            });
        });
    }
  • fileExists helper used to check if the data file (objtypes.txt) exists before searching.
    async function fileExists(filename: string): Promise<boolean> {
        const filePath = path.join(getDataDir(), filename);
        try {
            await fs.promises.access(filePath);
            return true;
        } catch {
            return false;
        }
    }
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 of behavioral disclosure. It states the tool searches a file but doesn't describe what the search returns (e.g., matches, full definitions, snippets), how results are ordered, whether it's case-sensitive, or any error conditions. For a search tool with zero annotation coverage, this is a significant gap in transparency about its behavior.

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 the core purpose without unnecessary words. Every part earns its place by specifying the action, target, and context concisely, 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 complexity of a search operation with no annotations and no output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., list of matches, structured data), how to interpret results, or any limitations (e.g., file size constraints, search performance). For a tool with 3 parameters and behavioral uncertainty, this leaves too much unspecified for reliable agent use.

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%, with clear documentation for all three parameters (query, page, pageSize). The description adds minimal value beyond the schema, only implying that the 'query' parameter searches within the file content. It doesn't explain search semantics (e.g., partial matches, wildcards) or how pagination interacts with results, so it meets the baseline for high schema coverage without compensating further.

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 target resource ('objtypes.txt file for object/item definitions in the game'), making the purpose immediately understandable. However, it doesn't explicitly differentiate this tool from its many sibling search tools (e.g., search_iftypes, search_invtypes) beyond mentioning the specific file name, which is helpful but could be more explicit about what makes 'objtypes' unique compared to other data types.

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. With multiple sibling tools like search_data_file, search_iftypes, etc., there's no indication of which tool is appropriate for searching object/item definitions specifically, nor any mention of prerequisites or contextual constraints. This leaves the agent to guess based on tool names alone.

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