clarify the definition of MCP opeartions

[biubiubiuboomboomboom]

Component(s)

router

Is your feature request related to a problem? Please describe.

Currently , MCP tool descriptions are generated from GraphQL operation comments , and tool names are fix (e.g execute_operation_ *). this approach may confuse user and lacks flexibility.

Describe the solution you'd like

I think we could :

• Allow users to define the MCP tool's name and use default generation rule like execute_operation_ * if name is empty.
• add a description field or declaration to define MCP tool's description .

Describe alternatives you've considered

No response

Additional context

No response

[github-actions]

WunderGraph commits fully to Open Source and we want to make sure that we can help you as fast as possible.
The roadmap is driven by our customers and we have to prioritize issues that are important to them.
You can influence the priority by becoming a customer. Please contact us here.

[Noroth]

Hi @biubiubiuboomboomboom,
thank you for the feedback. Adding another way to enrich the context for tools is a great idea. We will work on this as soon as possible.

[asoorm]

Just a quick update on this issue:

There has been a recent update to the GraphQL Spec (September 2025) which now permits Descriptions in Executable Definitions - Operations and Fragments.

• https://spec.graphql.org/September2025/#sec-Descriptions
• Add descriptions to executable documents | 2025 Update graphql/graphql-spec#1170

As such, we are looking to implement this support in the underlying https://github.com/wundergraph/graphql-go-tools/pull/1331/files library.

Then we can update the MCPServer in the Cosmo Router.