Skip to content

[feat] Actions should return values and the wrapper should decide what to do #640

@adrianriobo

Description

@adrianriobo

The main use case for mapt was to be used as a cli tool (wrapped on a container) as so the management for the outputs was done writing the content to a set of files. That logic was also included as part of the action layer.

On mapt-oss/mapt-mcp#1 mapt will be wrapped by an mcp server, the mcp server directly uses the action layer and may do not need to write the files.

  • This feat proposes to add return struct on eachaction with the current ouputs
  • Move the manage results functions (write to files) to the cli layer

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions