8000 MCP server require more and clearer data packaging types to support different business scenarios in a more user-friendly manner · Issue #823 · modelcontextprotocol/python-sdk · GitHub
[go: up one dir, main page]

Skip to content
MCP server require more and clearer data packaging types to support different business scenarios in a more user-friendly manner #823
Open
@cthulhu-tww

Description

@cthulhu-tww

Is your feature request related to a problem? Please describe.
I think the MCP server can clearly know what type of data response any function will return, such as any file, a large text data (from a database or elsewhere), and so on. The client only needs to determine the response type of the packaging, without verifying the data format. I think this is helpful for users to integrate MCP client into their system.

Describe the solution you'd like
I tried to submit a PR, but it was rejected. I accept the reason for rejection, although I still don't quite understand why it was rejected. If someone could have a better implementation method, or if someone could tell me how to better implement the above scenario, I would greatly appreciate it

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0