Skip to main content
Glama

Known issues, fixes and workarounds

find_known_issues
Read-only

Search what users report about AI agents and developer tools: known bugs, errors, fixes (with the version) and official workarounds, plus questions answered from official docs. Give an error message or a symptom (e.g. '401 Unauthorized codex', 'claude -p uses more of the limit', 'windows terminal flashing'). Each result links the GitHub issue and AgentGid's page; statuses update daily.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_known_issues"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemNoOptional: product slug or name, e.g. claude-code, openai-codex, cline
kindNo
limitNo
queryNoThe error message or symptom, in plain words

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, and the description adds genuinely useful behavior beyond that: results link the GitHub issue and an AgentGid page, and statuses refresh daily. That tells the agent what a result contains and how fresh it is, which the annotations do not. It does not mention result counts, pagination, or what happens when nothing matches, so it is strong but not exhaustive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with what the tool returns before the how-to-give-a-query guidance and the freshness note. The parenthetical examples are compact and earn their space by disambiguating query shape. Slightly dense but no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only, zero-required-parameter search with no output schema, the description covers purpose, query form, and return structure (issue link + page, daily-updated status). The main remaining gap is the meaning of the kind and limit parameters, which an agent would have to infer from the enum alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%, so the description should compensate — but it effectively restates the query parameter ('Give an error message or a symptom') that the schema already documents. The item parameter (product slug), the kind enum (agent/tool/mcp/skill/api/asset) and limit are not addressed at all, leaving half the inputs explained only by terse schema text.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource — searching user-reported known bugs, errors, versioned fixes, official workarounds and doc-answered questions — for AI agents and developer tools. The scope is narrow enough that an agent can distinguish it from sibling lookup tools like find_tools or how_to without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives concrete invocation guidance: 'Give an error message or a symptom' with three worked examples ('401 Unauthorized codex', 'claude -p uses more of the limit', 'windows terminal flashing'), which makes the intended query shape clear. It stops short of naming when-not-to-use cases or an alternative sibling, so it lands at clear context without exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources