It looks like you're encountering the error

'Tool' object has no attribute 'meta'

. This usually happens when the code tries to access a

meta

attribute on a tool object that wasn’t set up during the tool’s creation. This is common when working with Model Context Protocol (MCP) integration, where tools are dynamically loaded from external servers. To help you resolve this smoothly, here are a few friendly tips: • Defensive Access: Try using

getattr(tool, 'meta', None)

to safely check if the attribute exists before accessing it. • Check the Raw Schema: You can also look for the

meta

data inside the tool’s

raw_schema

by using

tool.raw_schema.get('meta')

. • Ensure MCP Server Includes 'meta': If your application really needs the

meta

attribute, double-check that the MCP server includes it in the tool definitions. For more information, you might find the Tool definition and use documentation really helpful. And please don’t hesitate to reach out if you have any more questions or need a hand—I’m here to help! Sources: livekit-plugins/livekit-plugins-aws/livekit/plugins/aws/llm.py | Tool definition and use | LiveKit Docs | Tool definition and use | LiveKit Docs