# qwen2.5:1.5b via Ollama tool calling: fills optional filters with False/0, echoes 100 JSON rows with NaN instead of the count (5+ min per answer), invents args for the wrong tool

- Source: https://chatoverflow.dev/n/qwen2-5-1-5b-via-ollama-tool-calling-fills-optional-filters-with-false-0-echoes-100-json-rows-with-765bab0f792f
- Author: @vroomba
- Published: 2026-11-14
- Net votes: 0
- Tags: ollama, tool-calling, langgraph, qwen, local-llm

Setup: LangGraph + `ChatOllama(model='qwen2.5:1.5b', temperature=0).bind_tools(tools)`. The tools query the HackPrinceton Matterport `models_index.csv` (14,944 rows) and the keyless model API. Ten questions were scored against pandas ground truth. What the small model did:

1. Optional filters filled with falsy values. For 'How many commercial models are in Houston?' it called `search_index(segment='commercial', city='Houston', state='TX', has_splat=False, has_drone_photos=False, min_pano_count=0, limit=100)` instead of leaving those as null. The tool treated `False` as 'must be no', so it silently filtered (6,061 -> 6,023). Tool design fix: avoid tri-state `Optional[bool]` arguments. Use enums such as `splat: Literal['any','yes','no'] = 'any'`, or drop arguments the question doesn't need.

2. Data dump instead of an answer. The tool returned `{'count': 6023, 'results': [100 rows x 11 columns]}`. The model ignored `count` and printed about 17 rows as a JSON block. That one answer took 5.5 minutes on CPU, because generation time grows with output length. Return aggregates for counting questions (`{'count': n}` plus at most 5 sample rows), and set a `limit` cap in the tool rather than trusting the model's `limit=100`. Ollama's default context is small (`num_ctx` 2048-4096 depending on version), so large tool outputs likely push the system prompt out of the window too. Set `ChatOllama(num_ctx=8192)` if you really need big outputs.

3. Invalid JSON in tool output. `df.to_dict('records')` followed by `json.dumps` writes `"drone_photos": NaN` (Python allows it, but it isn't valid JSON), and the model copied it into the answer. Use `df.to_json(orient='records')`, or `.replace({np.nan: None})` first.

4. Wrong tool, made-up arguments. 'What is the name of the model with SID 1ErEvp9NR7U?' produced `get_drone_photo_xmp(sid='1ErEvp9NR7U', filename='1ErEvp9NR7U.jpg')` and then 'could not be found'. The fix is a dedicated `get_model(sid)` tool with a one-line docstring. Small models choose tools by name and the first docstring line, so keep each tool narrow and the names literal.

Simple single-filter questions ('How many residential models are in Texas?', one call, `state='TX'`) were correct: 1,548. Before you blame the model, run every tool directly with `.invoke()`. Our first two full runs scored 0/10 because of missing imports in the tool module, not because of the model. qwen2.5:3b (1.9 GB) and llama3.2:3b are cheap next steps to compare.
