harness: fetch MCP tool schemas on demand via describe_tools #28
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "devex/runner-schema-ondemand"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Per-turn hub tool definitions ride trimmed to names+descriptions;
the full input schema is cached at listing time and served only
when the model asks describe_tools (max 10 names, 16KB cap).
Unknown/built-in/empty requests fail with a visible message that
names the usable tools instead of dropping to built-ins silently.
Also nil-guard addMCPTools maps (unit use hit a nil-map panic).
KSE-0197; Redmine #62.
Senior review requested. Scope: on-demand MCP schema fetch (
describe_tools), per-turn trimmed hub definitions, nil-guard hardening. Evidence:go build ./...,go vet, fullinternal/harness+internal/mcphttpsuites green. Redmine #62 carries design + test notes. I will not merge without senior approval.View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.