check_issue
Diagnoses known issues with a specific developer tool. Searches the graph for matched issues and returns solutions with confidence scores and related tools.
When to use
Call check_issue when you encounter a problem with a specific tool and want to see if it is a known issue with documented solutions. This tool is independent of the search flow and can be called at any time.
Be specific
issue_description for higher-confidence matches. Vague descriptions like "not working" will return lower confidence results.Input schema
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
tool_name | string | Required | — | Name of the tool to diagnose (e.g. "Prisma", "Next.js", "Docker"). |
issue_description | string | Required | — | Description of the problem you are experiencing. Be as specific as possible for better matches. |
tool_nameRequiredstringName of the tool to diagnose (e.g. "Prisma", "Next.js", "Docker").
issue_descriptionRequiredstringDescription of the problem you are experiencing. Be as specific as possible for better matches.
Examples
Database error diagnosis
Build/deployment issue
{
"tool_name": "Next.js",
"issue_description": "Dynamic routes return 404 in production build but work in dev mode"
}Runtime issue
{
"tool_name": "Docker",
"issue_description": "Container exits immediately with code 137 when running Node.js app"
}Response format
Returns an array of matched issues, each with a confidence score, description, solutions, affected versions, and related tools. Issues are ranked by confidence (highest first).
{
"tool_name": "Prisma",
"matched_issues": [
{
"title": "P3009: Migration failed — shadow database error",
"confidence": 0.92,
"description": "The P3009 error occurs when Prisma cannot create or access the shadow database used for migration diffing.",
"solutions": [
"Grant CREATE DATABASE permissions to the Prisma database user",
"Set the shadowDatabaseUrl in your Prisma schema to a dedicated shadow database",
"Use \"prisma migrate diff\" + \"prisma db execute\" as a workaround for environments where shadow databases are not supported"
],
"affected_versions": ["4.x", "5.x"],
"related_tools": ["PostgreSQL", "Supabase", "PlanetScale"]
},
{
"title": "PostgreSQL 16 compatibility issues with Prisma migrations",
"confidence": 0.78,
"description": "PostgreSQL 16 changed default permissions for the public schema, which can affect Prisma migrations.",
"solutions": [
"Run: GRANT ALL ON SCHEMA public TO your_db_user",
"Upgrade to Prisma 5.7+ which includes PostgreSQL 16 fixes"
],
"affected_versions": ["5.0–5.6"],
"related_tools": ["PostgreSQL"]
}
],
"total_matches": 2
}Confidence scores
Error codes
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
400 | Bad Request | Optional | — | Invalid or empty tool_name or issue_description. Both parameters must be non-empty strings. |
404 | Not Found | Optional | — | The specified tool was not found in the graph. Check the tool name spelling. |
500 | Internal Error | Optional | — | Graph query error. An unexpected failure occurred while searching for known issues. |
400OptionalBad RequestInvalid or empty tool_name or issue_description. Both parameters must be non-empty strings.
404OptionalNot FoundThe specified tool was not found in the graph. Check the tool name spelling.
500OptionalInternal ErrorGraph query error. An unexpected failure occurred while searching for known issues.
Related tools
search_tools— Find alternative tools if the issue is unresolvableget_stack— Build a new stack if you need to replace a problematic toolreport_outcome— Report the issue outcome to improve the knowledge base