Skip to content

mcpchecker action should support not enabling a toolset through the matrix #1414

Description

@Cali0707

In #1179 we are trying to add evals for a project without any toolset yet. Currently this flow will pass argocd as a toolset when starting the server, which will fail since that toolset does not exist.

The matrix approach should somehow allow for us to indicate whether or not a toolset needs to be enabled, or we just need to match a set of eval tasks to run

In general, we want to be able to run evals without any toolset being enabled, as for many projects the core toolset will support their needs and we just want to show compatibility

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    help wantedExtra attention is needed

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions