René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Bring back the concept of \"toolResult\" (non-chat result)","articleBody":"**Is your feature request related to a problem? Please describe.**\r\n\r\nI was working on an MCP client using the typescript SDK and saw `toolResult` as something I could get back from `callTool()`, but after opening [this issue](https://github.com/modelcontextprotocol/servers/issues/151) I was informed that `toolResult` is no longer a thing in the spec.\r\n\r\n**Describe the solution you'd like**\r\n\r\nI would like a non-chat-content way for tools to return the tool result, [this discussion](https://github.com/modelcontextprotocol/specification/discussions/90) is sort of touching on the same problem, maybe the LLM doesn't necessarily need the full tool result in the chat - maybe the client can choose to use it differently?\r\n\r\nI realize that simply an arbitrary \"result\" field is not a great solution in a spec and maybe that's why it was dropped, but having only one thing to return to the caller - the \"chat history\" - is very limiting. if `toolResult: any` is the temporary solution - I still think it has uses (if only for inspector-like tools).\r\n\r\n```ts\r\nreturn {\r\n    toolResult: results, // raw result object\r\n    content: [\r\n        {\r\n            type: 'text',\r\n            text: formattedResults, // formatted as chat-message\r\n        },\r\n    ],\r\n    isError: false,\r\n};\r\n```\r\n\r\nThanks","author":{"url":"https://github.com/Madd0g","@type":"Person","name":"Madd0g"},"datePublished":"2024-12-04T14:50:48.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":36},"url":"https://github.com/97/modelcontextprotocol/issues/97"}