New MCP tools:
- basis_movement: aggregated basis trend, one headline line per crop. The cheap
"how is basis moving overall" view; optional commodity/source/delivery/days.
- basis_detail: per-(elevator, crop, delivery) basis first→last drill-down.
Both do the aggregation MCP-side and return compact markdown to keep token
burn low, so a client can call the cheap aggregate first and drill in only when
needed.
Flexibility/parity changes:
- price_history: commodity is now optional (spans all crops); groups by
(source, commodity, delivery); surfaces basis first→last in the summary and
adds a futures column to the raw table.
- latest_prices: expose the `kind` filter (grain/fertilizer) that the API and
client already supported.
- client.history(): commodity optional.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Exposes live + historical ag-bids commodity data (from the ag-monitor
service at agbids.paul.farm) as MCP tools, sitting behind MetaMCP at
https://mcp.jpaul.io/metamcp/ag-bids/mcp.
Pattern mirrors zerto-docs-rag with one addition: HTTP Basic auth in
front of the streamable-HTTP transport so namespace guessers can't reach
the tools. Stdio transport is unaffected (used by local Claude Desktop
dev).
Tools (markdown returns, ~15 LOC each):
best_local_bid(commodity) — where to sell corn/soy/wheat today,
for the current calendar month only
current_lime_price() — latest lime quotes ($/ton)
current_input_price(product?) — MAP / Potash / Lime
latest_prices(...) — filtered snapshot
price_history(...) — per-(source,delivery) trend
list_sources / list_commodities / list_deliveries
source_health() — healthy / stale / down buckets
todays_summary() — same shape as morning brief snapshot
Data path: ag-bids-mcp -> X-API-Key -> /api/data/* on ag-monitor
(reuses BRIEF_API_KEY).
Tests: 24 covering the httpx client, markdown formatters, HTTP Basic
middleware (401/200), and JSONL usage logging.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
justin