Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Enrich the server definition to support the right selection (ServerCapabilities?) #79

@dmartinol

Description

@dmartinol

Registered servers should provide a detailed definition of the skills/capabilities provided to support server selection, as if the registry were an MCP server of MCP servers (which probably shouldn't be a bad idea).

Currently, servers are described by a generic description field that we might suggest making as specific as possible, but after all, the description means everything and nothing.

Being more prescriptive in the specifications and adding fields to support the selection of the right tool would probably simplify the job of the AI ​​administrator (or the agent that automatically selects the server to satisfy a given request). E.g., think of having more servers providing the same interactions with a given external system: how could we differentiate b/w them and pick the right one?

BTW: metadata is probably a more generic concept that could include the skills/capabilities together with other relevant attributes (e.g. security related options) for differentiation and selection purposes.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestnot go-live blockerThis issue has been reviewed and determined to not be a blocker to go-liveserver.json

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions