Add file system reading tool for Eco server data access #762

Closed
opened 2026-08-14 01:43:03 +00:00 by coilyco-ops-gaming · 1 comment

Request

Add a file system reading tool that can retrieve information from the Eco server's data files, similar to how other tools in this service access trade history and economy data.

Context

The service currently has tools for accessing Eco server data (trade watchers, market data, economy stats), but lacks a general-purpose file system reader that could access raw server data files directly. This would enable:

  • Reading configuration files
  • Accessing raw trade logs
  • Inspecting server state files
  • Debugging data pipeline issues

Proposed change

Add a tool (e.g., eco__read_file or similar) that can read files from the Eco server's data directory, with appropriate access controls and path validation to prevent unauthorized file access.

## Request Add a file system reading tool that can retrieve information from the Eco server's data files, similar to how other tools in this service access trade history and economy data. ## Context The service currently has tools for accessing Eco server data (trade watchers, market data, economy stats), but lacks a general-purpose file system reader that could access raw server data files directly. This would enable: - Reading configuration files - Accessing raw trade logs - Inspecting server state files - Debugging data pipeline issues ## Proposed change Add a tool (e.g., `eco__read_file` or similar) that can read files from the Eco server's data directory, with appropriate access controls and path validation to prevent unauthorized file access.
Member

Moved to coilyco-gaming/eco-app#303 and closing here.

Forgejo has no cross-repo move, so the issue was recreated in the target repo with the body verbatim plus a provenance footer pointing back at this thread. Comments were not copied, so this thread stays the record for anything said here.

Flagged on the copy: eco-app#42, #243 and #244 all cover on-disk Eco server state through an MCP surface, so the receiving repo should confirm this is distinct before building it.

Relocated by Darren (director seat) during the 2026-08-15 sirens-echo triage pass, acting on the move-to-repo/coilyco-gaming-eco-app label. Reversible: reopen this issue and close the copy.

Moved to coilyco-gaming/eco-app#303 and closing here. Forgejo has no cross-repo move, so the issue was recreated in the target repo with the body verbatim plus a provenance footer pointing back at this thread. Comments were not copied, so this thread stays the record for anything said here. Flagged on the copy: eco-app#42, #243 and #244 all cover on-disk Eco server state through an MCP surface, so the receiving repo should confirm this is distinct before building it. Relocated by Darren (director seat) during the 2026-08-15 sirens-echo triage pass, acting on the `move-to-repo/coilyco-gaming-eco-app` label. Reversible: reopen this issue and close the copy.
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
coilyco-gaming/sirens-echo#762
No description provided.