Skip to main content
Glama
zad0xlik

RateSpot MCP Server

by zad0xlik

read-file

Access and retrieve file content by specifying the file path, enabling integration with RateSpot MCP Server for mortgage rate APIs and lending information.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesPath to the file to read

Implementation Reference

  • Core implementation of file reading: retrieves file info, checks if binary, reads the file synchronously, decodes using detected encoding, and returns content.
    static readFile(filePath: string) {
      const info = this.getFileInfo(filePath);
      
      if (info.isBinary) {
        throw new Error('Cannot read binary files');
      }
    
      const buffer = fs.readFileSync(filePath);
      const encoding = info.encoding || 'utf8';
      const content = iconv.decode(buffer, encoding);
    
      return {
        content,
        encoding,
        info
      };
    }
  • Input schema for the read-file tool: requires a 'path' string parameter.
    {
      path: z.string().describe("Path to the file to read")
    },
  • Registers the 'read-file' MCP tool with schema and a handler that delegates to FileAnalyzer.readFile and handles response formatting and errors.
    server.tool(
      "read-file",
      {
        path: z.string().describe("Path to the file to read")
      },
      async (params) => {
        try {
          const result = await FileAnalyzer.readFile(params.path);
          return {
            content: [{
              type: "text",
              text: result.content
            }]
          };
        } catch (error) {
          return {
            content: [{
              type: "text",
              text: `Error reading file: ${error instanceof Error ? error.message : String(error)}`
            }],
            isError: true
          };
        }
      }
    );
  • Supporting method called by readFile to get file stats, detect MIME type, binary nature, and text encoding.
    static getFileInfo(filePath: string) {
      const stats = fs.statSync(filePath);
      const ext = path.extname(filePath);
      const buffer = fs.readFileSync(filePath);
      
      // Detect MIME type
      let mimeType = this.getMimeTypeFromExtension(ext);
      if (fileType.fileTypes) {
        for (const [type, signature] of Object.entries(fileType.fileTypes)) {
          if (Array.isArray(signature) && 
              buffer.length >= signature.length &&
              signature.every((byte, i) => buffer[i] === byte)) {
            mimeType = `image/${type}`;
            break;
          }
        }
      }
    
      const isBinary = this.isBinaryFile(buffer);
      let encoding: string | undefined;
    
      // Try to detect encoding for text files
      if (!isBinary) {
        try {
          // Try UTF-8 first
          const content = buffer.toString('utf8');
          if (this.isValidUtf8(content)) {
            encoding = 'utf8';
          } else {
            // Try other common encodings
            const encodings = ['ascii', 'utf16le', 'latin1'];
            for (const enc of encodings) {
              try {
                iconv.decode(buffer, enc);
                encoding = enc;
                break;
              } catch {
                continue;
              }
            }
          }
        } catch {
          // If all encoding detection fails, default to binary
        }
      }
    
      return {
        path: filePath,
        size: stats.size,
        created: stats.birthtimeMs,
        modified: stats.mtimeMs,
        mimeType,
        extension: ext,
        isBinary,
        encoding
      };
    }
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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/zad0xlik/ratespot-mcp'

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