get_species reports "admin API key missing" while every other admin-backed tool has access #219

New issue

Closed

opened 2026-08-12 23:13:07 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-08-12 23:13:07 +00:00

Member

QA sweep, Eco via Sirens, day 40, 2026-08-12.

Observed

get_species(name="Snapping Turtle") returns taxonomy, wiki extract and photo, but:

{"error":"population data unavailable (admin API key missing)",
 "population":[],"populationFirst":null,"populationLatest":null,"populationDelta":null}

Contradiction

The admin key is present and working in the same session:

get_region → adminAvailable: true, and it carries the population for this exact species: SnappingTurtleSpecies current 110, observed peak 130, 5,770 samples, freshness: "current".
get_economy, get_climate → admin_ok: true.
get_trades, get_stores, get_civics, get_progression, get_world all returned admin-backed data.

So get_species has its own key/credential path and it is broken, or it is misattributing a different failure to a missing key.

Expected

Population history for the requested species, from the same source get_region already reads.

Secondary

The error message is misleading for operators — it will send someone hunting for a key that is configured. If the real failure is a different lookup, say that.

QA sweep, Eco via Sirens, day 40, 2026-08-12. ## Observed `get_species(name="Snapping Turtle")` returns taxonomy, wiki extract and photo, but: ```json {"error":"population data unavailable (admin API key missing)", "population":[],"populationFirst":null,"populationLatest":null,"populationDelta":null} ``` ## Contradiction The admin key is present and working in the same session: - `get_region` → `adminAvailable: true`, and it carries the population for this exact species: `SnappingTurtleSpecies` current 110, observed peak 130, 5,770 samples, `freshness: "current"`. - `get_economy`, `get_climate` → `admin_ok: true`. - `get_trades`, `get_stores`, `get_civics`, `get_progression`, `get_world` all returned admin-backed data. So `get_species` has its own key/credential path and it is broken, or it is misattributing a different failure to a missing key. ## Expected Population history for the requested species, from the same source `get_region` already reads. ## Secondary The error message is misleading for operators — it will send someone hunting for a key that is configured. If the real failure is a different lookup, say that.

coilyco-ops referenced this issue

2026-08-12 23:34:54 +00:00

Tracking: 2026-08-12 full-surface QA sweep of the eco MCP (22 tools, 23 findings) #240

coilyco-ops referenced this issue

2026-08-12 23:36:09 +00:00

Tracking: 2026-08-12 full-surface QA sweep of the eco MCP (22 tools, 23 findings) #240

coilyco-ops referenced this issue

2026-08-12 23:47:23 +00:00

Tracking: 2026-08-12 full-surface QA sweep of the eco MCP (22 tools, 23 findings) #240

coilyco-ops referenced this issue from a commit

2026-08-13 06:09:29 +00:00

fix(species): use the same admin key every other tool uses