Fix: path param should be optional

[almaleksia]

Summary

Treating path param of get_file_contents as optional + trimming leading slash.

Why

Param path is optional in tool description but in the tool handler we treat it as required parameter and get bunch of failures because LLM doesn't pass this parameter.

Trimming leading slash in path so that we do not end up calling <owner>/<repo>/contents//<path> which results in 404.

MCP impact

• No tool or API changes
• Tool schema or behavior changed
• New tool added

Prompts tested (tool changes only)

Tested in MCP inspector.

Security / limits

• No security or limits impact
• Auth / permissions considered
• Data exposure, filtering, or token/size limits considered

Lint & tests

• Linted locally with ./script/lint
• Tested locally with ./script/test

Docs

• Not needed
• Updated (README / docs / examples)

[Copilot]

Pull request overview

This PR fixes the get_file_contents tool to treat the path parameter as optional (matching the schema definition) and trims leading slashes from paths to prevent double-slash API calls that result in 404 errors.

Key Changes:

• Changed from RequiredParam to OptionalParam for the path parameter to align handler implementation with schema
• Added strings.TrimPrefix(path, "/") to prevent malformed API paths like /owner/repo/contents//file

[SamMorrowDrums]

Yaass!!!