Relationships
#1349 Extension/type search at method granularity — find capabilities, not just packages
Opened by jeremy · 7/22/2026
Problem
swamp extension search matches on extension-level name and description. swamp model type search matches on type names. Neither searches method descriptions or output schemas.
When composing multiple models, the question is: "which method across all installed (or registry) types gives me this specific data?" Today that requires reading full type describe output for each candidate — expensive in both time and tokens.
Concrete example
Needed: the source branch of a GitLab merge request (to check out code for a doc-fact-check review).
swamp model type search gitlab→ found@webframp/gitlabget_merge_request→ returns mergeability status but notsourceBranch- Eventually discovered
@webframp/gitlab-review/get_mr_diffreturnssourceBranch— only after trial-and-error with a different extension
Extension descriptions didn't help distinguish: "Read and write GitLab data via GraphQL" vs "AI-assisted GitLab merge request code review" — neither suggests which one returns source branch metadata.
Proposal
Make search method-aware:
- Index method descriptions and output field names in addition to extension/type-level metadata
- Return results at method granularity — e.g.
swamp extension search "source branch"→@webframp/gitlab-review / get_mr_diff (outputs: sourceBranch, targetBranch, diffs) - For
swamp model type search(local types), optionally search method descriptions too
Relationship to #825
Issue #825 shipped extension info --json with type+method data — solving "inspect before you pull." This request is the layer above: finding which extension to inspect in the first place, when you know the capability you need but not which package contains it.
Impact
Reduces multi-model composition from trial-and-error (pull → describe → wrong one → try next) to a single search → match → use flow. Particularly impactful for agents doing autonomous composition.
Open
No activity in this phase yet.