accuweather Tool

An LLM has no idea what the weather is right now, anywhere - that's outside what any language model can know from training alone. accuweather Tool is comfyui_LLM_party's fix for that specific gap: it wraps AccuWeather's API into a tool your agent can call mid-conversation, so a question like "what's the weather like in Shanghai" gets a real, current answer instead of a plausible-sounding guess.

Like this pack's other *_tool nodes (Amap Reverse Geocoding, the Neo4j knowledge-graph toolkit), what it outputs isn't meant for you to read directly - it's a tool definition, wired into the pack's LLM/agent node's tool-list input, that the model decides whether and when to invoke based on the conversation.

The inputs and outputs that matter

• city (default Shanghai) - the city to check. The Chinese-market default here isn't an accident - it's the same texture you'll notice across several of this pack's tools (Amap's default coordinates sit in Beijing, Neo4j's default password matches a common local-dev convention): this is a project built primarily for a Chinese-speaking user base, with defaults that reflect that even though the tools themselves work anywhere the underlying API has coverage.
• accuweather_key - your own AccuWeather API key. Empty by default; you need to supply your own.
• is_enable - the pack's standard bypass toggle.

Output: tool (STRING) - the serialized tool definition, wired into an agent node, not displayed.

How to install it

Search comfyui_LLM_party in ComfyUI Manager and install, then restart. Manual route:

cd ComfyUI/custom_nodes
git clone https://github.com/heshengtao/comfyui_LLM_party.git

Run pip install -r requirements.txt from inside the pack's folder using ComfyUI's own Python, then restart. Beyond the base install, this node needs a working AccuWeather API key - sign up for one through AccuWeather's own developer portal (they offer a free tier for basic usage) and drop it into accuweather_key.

Common issues & troubleshooting

Nothing comes back, or the agent reports the tool failed. Check accuweather_key first - an empty, expired, or rate-limited key fails the request before any weather data comes back. AccuWeather's free tier has real call limits; if you're testing this repeatedly in a short window, you can hit those limits faster than expected.

The city resolves to the wrong place, or fails to resolve at all. Weather APIs generally need enough specificity to disambiguate a city name from others sharing it worldwide - a bare city name without a country or region qualifier can resolve incorrectly, especially for common names. If lookups seem to hit the wrong location, try adding a country to the city field rather than assuming the tool is broken.

The agent never reaches for this tool at all. Same as any tool-calling node in this pack - the LLM only uses a tool if its system prompt or the conversation gives it reason to. If your agent isn't checking the weather when you'd expect it to, make sure its instructions actually mention it has that capability, rather than assuming the tool's mere presence in the tool list is enough.