mirror of https://github.com/hanzoai/insights.git synced 2026-10-30 16:15:31 +00:00

Files

T

History

zeekay e552a2f764 Point the MCP tools at /v1/

The generator already resolves operations under /v1/ (40d120dbf7), and
the Python docstrings and prompts it copies say /v1/ too, but the
checked-in output still carried upstream's /api/ paths, so 771 tool
calls went to a prefix insights no longer serves.  Bring the generated
tools, types and schema in line with what the generator emits for the
/v1/ mount, and move the tests that assert those paths.

Left as they are: POST /api/orders and /api/feed are customer span
names in tool examples, and the connection tool's `api/projects/2/...`
mirrors insights_connection.py's help text.

Claude-Session: https://claude.ai/code/session_01TUxvfuta1Z44KVNYuAz71F

2026-09-24 15:00:46 -07:00

apps

Point the MCP tools at /v1/

2026-09-24 15:00:46 -07:00

prompts

…

error_tracking_alerts.yaml

chore: rebase the tree onto upstream master fa1a9a60

2026-08-06 01:25:36 -07:00

README.md

…

tools.yaml

…

README.md

Error tracking MCP definitions

error_tracking_alerts.yaml is a subset file (not synced by scaffold-yaml --sync-all beyond validation) that wraps the generic insights_functions_* operations as error-tracking alert tools.

Maintainer notes:

Tool descriptions and the authoring-error-tracking-alerts skill ship to external MCP clients — never reference repo paths or internal code in them.
The block payloads embedded in the create-tool description and in products/error_tracking/skills/authoring-error-tracking-alerts/references/block-templates.md mirror INSIGHTS_FUNCTION_SUB_TEMPLATES (error-tracking entries) in frontend/src/scenes/insights-functions/sub-templates/sub-templates.ts — keep them in sync when the sub-templates change.
Comments in error_tracking_alerts.yaml do not survive scaffold-yaml --sync-all (the file is re-emitted with a fixed header), which is why these notes live here.