You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat: surface why_recommended and declare capability/cost/provider fields (#102)
* feat: surface why_recommended and declare capability/cost/provider fields
The live Discover/Inspect APIs now return why_recommended, capabilities
(standardized descriptors with coverage tags), expected_cost,
provider_id and provider_logo_url, but the toolkit neither displayed
nor declared them.
- CLI: discover output renders a 'why:' line with the recommendation
reason (truncated at 160 chars), so agents see ranking rationale.
- Python SDK: adds ToolCapability/ToolCapabilityTag models; ToolInfo
gains capabilities, expected_cost, why_recommended, provider_id and
provider_logo_url.
- MCP: same additions to the hand-written ToolInfo declarations.
- OpenAPI spec: documents why_recommended, capabilities (new
PublicToolCapability/PublicCapabilityTag schemas) and
provider_logo_url on PublicCapabilityResult; artifacts regenerated.
Advances #65 (why_recommended display sub-task).
* feat(cli): show capabilities and expected_cost in inspect output
inspect responses include standardized capability descriptors and a
pre-call cost estimate; render them in the metadata table:
Capability: MKT.BARS.ADJUSTED (US, CN, HK, JP, UK, DE, KR, IN, +2 more)
Est. cost: 24.2 credits
Coverage tag lists are capped at 8 entries. Malformed or absent
fields render nothing.
0 commit comments