REPOSITORY ANALYSIS

composio

An optional TypeSafe provider for Composio that uses Jev to choose among tools and bounded argument options.

E2 · source reviewedPublic material or source evidence was reviewed. A fixed-version source review requires checking a pinned revision; this is not a reproduction, performance endorsement, or safety guarantee.
Stars
30,300
Forks
4,819
License
MIT
Last commit
2026-09-23

What Jev does here

Uses a routing Choice, Noul action gates and finite argument questions, then returns abstain, partial or call. Missing required arguments remain explicit; destructive tool calls retain a confirmation requirement.

Separates selecting a tool from binding its arguments and executing it, allowing callers to handle no-action, uncertainty and partial inputs explicitly.

Pinned provider decision code reviewed, not a live Composio run. The adapter's thresholds and required-confirmation flag are application rules; they do not prove safe execution unless the caller enforces them.

What task does this project fit?

Choose a registered Composio tool and bind only supported arguments from a request.

Material analysed:

From input to action

  1. Normalize request/context and form route plus action-gate questions.
  2. Use fan-out when within budget, otherwise route before asking arguments.
  3. Return abstain, partial or call; destructive calls retain confirmation metadata.

Implementation details that matter

A missing argument is not a guessed value

The adapter distinguishes not_stated, confident values and low-confidence suggestions. Required missing arguments produce partial rather than a complete call.

Inspect the supporting source ↗

Destructive routing has a non-lowerable floor

resolveThresholds enforces at least 0.9 routing for destructive tools. The returned requiresConfirmation flag still needs a caller that actually honors it.

Inspect the supporting source ↗

When to choose it

Useful for tools with finite, typed argument domains and explicit missing-input handling. Do not expect it to freely generate arbitrary argument text or execute a returned call safely by itself.

How to inspect it yourself

Follow fan_out versus route_then_arguments, then inspect missing, suggestions and requiresConfirmation in the final result. Test an omitted required field and a destructive tool with a low configured threshold.

Limits of this review

  • No Composio integration or paid call was run.
  • The 254-tool cap is a constraint of this fixed adapter's 255-option routing question plus none, not a universal service limit.
Primary material used in this analysis