Recommendations · Jinear (demo) · as of 27 Aug 2026

9 open.

1 high4 medium4 low
ToolTypeFindingImpact
High1 open
save_issuev1Contract fixAgents are failing to set issue priority with strings.

What to change

Update the `priority` argument to accept string values like 'High' or 'Low' in addition to integers, or update its description to clarify that only integer values are supported.

The primary failure mode is `arg:schema_violation` because agents are attempting to pass string names for priority instead of the required integer.

Impact

102
sessions affected
28%
first-try success
15.1k
tokens wasted

Failure mix

Arg type violation66Backend unreachable57Rate limited25Entity not found6Empty result1
After failing here, agents switched to list_issues, get_issue, list_issue_statuses, get_userNo earlier recorded version to compare.confidence: high
Medium4 open
list_issuesv1InvestigateTool is unreliable due to frequent upstream dependency failures.

Heads-up

Investigate the root cause of the high rate of `dep:upstream_unreachable` and `dep:rate_limited` errors with the backend service.

The primary failure mode is backend unavailability, leading to a high unresolved task rate and user-facing errors.

Impact

126
sessions affected
62%
first-try success
5.0k
tokens wasted

Failure mix

Backend unreachable77Rate limited23Empty result4Arg type violation4
After failing here, agents switched to save_issue, list_projects, list_issue_statuses, get_issueNo earlier recorded version to compare.confidence: high
get_issuev1InvestigateHigh rate of backend failures and entity not found errors.

Heads-up

Investigate the high rate of 'dep:upstream_unreachable' and 'resource:not_found' errors; the former suggests a backend health issue, while the latter may indicate the model is hallucinating issue IDs.

A significant portion of calls fail due to backend timeouts or because the requested issue does not exist, leading to a high rate of unresolved tasks and tool abandonment.

Impact

41
sessions affected
66%
first-try success
812
tokens wasted

Failure mix

Backend unreachable9Entity not found9Rate limited2
After failing here, agents switched to list_issues, list_usersNo earlier recorded version to compare.confidence: high
list_issue_labelsv1InvestigateHigh rate of backend dependency failures causing unresolved tasks.

Heads-up

Investigate the high incidence of `dep:upstream_unreachable` and `dep:rate_limited` errors with the backend service.

The primary failure mode is backend dependency errors, which the tool owner cannot fix via the contract and require upstream investigation.

Impact

23
sessions affected
59%
first-try success
596
tokens wasted

Failure mix

Backend unreachable10Rate limited3
After failing here, agents switched to list_teams, list_project_labels, save_issueNo earlier recorded version to compare.confidence: high
get_projectv1InvestigateHigh rate of backend timeouts when retrieving projects.

Heads-up

Investigate the high rate of 'database connection timeout' errors with the backend service responsible for project lookups.

A significant portion of calls are failing due to upstream dependency issues, making the tool unreliable.

Impact

10
sessions affected
61%
first-try success
320
tokens wasted

Failure mix

Backend unreachable7
After failing here, agents switched to list_teams, list_projectsNo earlier recorded version to compare.confidence: high
Low4 open
get_documentv1Capability gapTool fails frequently when users guess document IDs/slugs.

What to change

Add a search capability to the tool, or guide the model to use `list_documents` first to find a valid ID before calling `get_document`.

The tool is almost always called with non-existent IDs, leading to a high rate of unresolved tasks and abandonment.

Impact

12
sessions affected
0%
first-try success
581
tokens wasted

Failure mix

Entity not found10Rate limited1Empty result1
After failing here, agents switched to list_documentsNo earlier recorded version to compare.confidence: high
list_projectsv1InvestigateTool is failing frequently due to upstream dependency issues.

Heads-up

Investigate the high rate of `dep:upstream_unreachable` and `dep:rate_limited` errors with the backend service that serves project lists.

The primary driver of failure is unresolved tasks, caused almost entirely by backend dependency errors that the tool owner cannot fix via the contract.

Impact

68
sessions affected
77%
first-try success
1.1k
tokens wasted

Failure mix

Backend unreachable12Rate limited12Empty result1
After failing here, agents switched to list_teams, get_project, list_issues, save_issueNo earlier recorded version to compare.confidence: high
list_teamsv1InvestigateHigh rate of backend failures causing unresolved tasks.

Heads-up

Investigate the high rate of `dep:upstream_unreachable` and `dep:rate_limited` errors with the backend service owner.

The primary failure mode is backend dependency errors, which are outside the tool contract owner's direct control but are severely impacting user success.

Impact

43
sessions affected
66%
first-try success
737
tokens wasted

Failure mix

Backend unreachable12Rate limited5Empty result2
After failing here, agents switched to list_projects, list_project_labels, list_issues, save_issueNo earlier recorded version to compare.confidence: high
get_diffv1InvestigateTool is mocked but failing with backend dependency errors.

Heads-up

Investigate why a mocked tool is returning `dep:upstream_unreachable` errors like 'internal server error' and 'database connection timeout'.

The tool is marked as mocked, but its primary failure mode is unreachable backends, which should not happen.

Impact

8
sessions affected
56%
first-try success
647
tokens wasted

Failure mix

Backend unreachable12Empty result1
No earlier recorded version to compare.confidence: high
16tools healthy · no actionshow
create_attachmentcreate_issue_labelget_issue_statusget_status_updatesget_teamlist_cycleslist_documentslist_issue_statuseslist_milestoneslist_project_labelslist_userssave_commentsave_documentsave_milestonesave_status_updatesearch_documentation