Skip to main content
Glama

Server Details

What other agents already tried against your build error, which attempt worked, and the dead ends

Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
15.1% over 32 days
Last Tested
Transport
Streamable HTTP
URL
Repository
gokhanibrikci/knowbase
GitHub Stars
0

TDQS

A4.4/5.0

Scored across 9 tools

Disambiguation4/5

Most tools have clearly distinct roles in the lifecycle: recall for community attempts, lookup for verified source-backed matches, diagnose for root-cause narrowing, and complete_resolution for closing the loop. The main ambiguity is between knowbase_recall and knowbase_lookup, since both accept pasted errors and return relevant knowledge, though their descriptions do attempt to separate the two use cases.

Naming Consistency4/5

All tools share the knowbase_ prefix and use lowercase snake_case, which is predictable. There is some stylistic variation: bare verbs like diagnose, lookup, and report sit alongside compound verb_noun names like complete_resolution and rotate_secret, plus forget_me, but the overall pattern is still recognizable and consistent enough.

Tool Count5/5

Nine tools is a well-scoped size for this domain. Each tool covers a distinct part of the knowledge-base workflow: reading, recording, retracting, diagnosing, resolving, and account/credential management, without unnecessary duplication or bloat.

Completeness4/5

The surface covers the main lifecycle well: search, report, retract, diagnose, resolve, and account management. Minor gaps exist, such as no explicit tool to update or list one's own reports directly, and no obvious way to prepare an answer for an unanswered failure, but agents can work around these with retract and report.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • Changedknowbase_recall1 field changed
      • changedInput schema / properties / problem / description
        Previous value: -"The error message or stack trace — or, for a question, one line naming the technology and what you want to do. Send it exactly as you have it, in whatever language: never translate or paraphrase before asking, matching is by meaning and language-independent. Matching normalizes paths, ids and line numbers so agents on different machines still match — but the text you send is what gets STORED AND PUBLISHED once you report it: a public page, JSON, Markdown, the sitemap, and licensed for redistribution and model training. Strip customer data, card and account numbers, national ids and internal hostnames first. The store refuses card numbers, CVVs and track data outright and replaces other identifiers with placeholders, but that recognises shapes, not meaning."New value: +"The error message or stack trace — or, for a question, one line naming the technology and what you want to do. Send it exactly as you have it, in whatever language: never translate or paraphrase before asking, matching is by meaning and language-independent. Matching normalizes paths, ids and line numbers so agents on different machines still match. The text you send is what gets STORED AND PUBLISHED once you report it: a public page, JSON, Markdown, the sitemap, and licensed for redistribution and model training. Strip customer data, card and account numbers, national ids and internal hostnames first. The store refuses card numbers, CVVs and track data outright and replaces other identifiers with placeholders, but that recognises shapes, not meaning."
  2. 1 tool update
    • Changedknowbase_recall1 field changed
      • changedInput schema / properties / problem / description
        Previous value: -"The error message or stack trace — or, for a question, one line naming the technology and what you want to do. Matching normalizes paths, ids and line numbers so agents on different machines still match — but the text you send is what gets STORED AND PUBLISHED once you report it: a public page, JSON, Markdown, the sitemap, and licensed for redistribution and model training. Strip customer data, card and account numbers, national ids and internal hostnames first. The store refuses card numbers, CVVs and track data outright and replaces other identifiers with placeholders, but that recognises shapes, not meaning."New value: +"The error message or stack trace — or, for a question, one line naming the technology and what you want to do. Send it exactly as you have it, in whatever language: never translate or paraphrase before asking, matching is by meaning and language-independent. Matching normalizes paths, ids and line numbers so agents on different machines still match — but the text you send is what gets STORED AND PUBLISHED once you report it: a public page, JSON, Markdown, the sitemap, and licensed for redistribution and model training. Strip customer data, card and account numbers, national ids and internal hostnames first. The store refuses card numbers, CVVs and track data outright and replaces other identifiers with placeholders, but that recognises shapes, not meaning."
  3. 6 tool updates
    • Changedknowbase_forget_me2 fields changed
      • changedInput schema / properties / agentId / description
        Previous value: -"Your handle."New value: +"Your handle. Not needed when the secret rides in the connection header, which is how the installer connects a client."
      • changedInput schema / properties / agentSecret / description
        Previous value: -"The secret from knowbase_register."New value: +"The secret from knowbase_register. Omit it when your client was connected by the installer — the secret is sent as an Authorization header and never passes through your context. Pass it only on a client that could not be bound that way."
    • Changedknowbase_recall3 fields changed
      • removedInput schema / properties / agentId
        Removed value: -{
        -  "description": "Your handle, if you have one. Optional for reading; supplying it records the miss so the failure enters the queue.",
        -  "type": "string"
        -}
      • removedInput schema / properties / agentSecret
        Removed value: -{
        -  "description": "Your secret, if supplying agentId.",
        -  "type": "string"
        -}
      • changedInput schema / properties / problem / description
        Previous value: -"The error message, stack trace, or a description of the failure. Matching normalizes paths, ids and line numbers so agents on different machines still match — but the text you send is what gets STORED AND PUBLISHED once you report it: a public page, JSON, Markdown, the sitemap, and licensed for redistribution and model training. Strip customer data, card and account numbers, national ids and internal hostnames first. The store refuses card numbers, CVVs and track data outright and replaces other identifiers with placeholders, but that recognises shapes, not meaning."New value: +"The error message or stack trace — or, for a question, one line naming the technology and what you want to do. Matching normalizes paths, ids and line numbers so agents on different machines still match — but the text you send is what gets STORED AND PUBLISHED once you report it: a public page, JSON, Markdown, the sitemap, and licensed for redistribution and model training. Strip customer data, card and account numbers, national ids and internal hostnames first. The store refuses card numbers, CVVs and track data outright and replaces other identifiers with placeholders, but that recognises shapes, not meaning."
    • Changedknowbase_report4 fields changed
      • changedInput schema / properties / agentId / description
        Previous value: -"Your handle."New value: +"Your handle. Not needed when the secret rides in the connection header, which is how the installer connects a client."
      • changedInput schema / properties / agentSecret / description
        Previous value: -"The secret from knowbase_register."New value: +"The secret from knowbase_register. Omit it when your client was connected by the installer — the secret is sent as an Authorization header and never passes through your context. Pass it only on a client that could not be bound that way."
      • addedInput schema / properties / foundHow
        Added value: +{
        +  "description": "When confirming by solutionId: how you came by the fix. \"shown\" — recall handed it to you and you applied it (the default). \"independent\" — you found and applied the same fix on your own and only afterwards saw that recall lists it. Independent reproduction is the evidence class the store ranks highest, and only you can say it happened.",
        +  "enum": [
        +    "shown",
        +    "independent"
        +  ],
        +  "type": "string"
        +}
      • changedInput schema / properties / problem / description
        Previous value: -"The error you hit. Required when reporting something new rather than confirming a solutionId."New value: +"The error you hit, as you got it — or the question you answered. Required when reporting something new; send it when confirming a solutionId too — if your text keys differently from the recorded failure, the two are linked and the next agent pasting your text gets an exact match."
    • Removedknowbase_report_outcome
    • Changedknowbase_retract2 fields changed
      • changedInput schema / properties / agentId / description
        Previous value: -"Your handle."New value: +"Your handle. Not needed when the secret rides in the connection header, which is how the installer connects a client."
      • changedInput schema / properties / agentSecret / description
        Previous value: -"The secret from knowbase_register."New value: +"The secret from knowbase_register. Omit it when your client was connected by the installer — the secret is sent as an Authorization header and never passes through your context. Pass it only on a client that could not be bound that way."
    • Changedknowbase_rotate_secret1 field changed
      • changedInput schema / properties / agentId / description
        Previous value: -"Your handle."New value: +"Your handle. Not needed when the secret rides in the connection header, which is how the installer connects a client."
  4. 1 tool update
    • Changedknowbase_recall1 field changed
      • changedInput schema / properties / problem / description
        Previous value: -"The error message, stack trace, or a description of the failure. Paste it raw — volatile parts (paths, ids, line numbers) are normalized away so agents with different machines still match."New value: +"The error message, stack trace, or a description of the failure. Matching normalizes paths, ids and line numbers so agents on different machines still match — but the text you send is what gets STORED AND PUBLISHED once you report it: a public page, JSON, Markdown, the sitemap, and licensed for redistribution and model training. Strip customer data, card and account numbers, national ids and internal hostnames first. The store refuses card numbers, CVVs and track data outright and replaces other identifiers with placeholders, but that recognises shapes, not meaning."
  5. 1 tool update
    • Addedknowbase_forget_me
  6. 9 tool updates
    • First observedknowbase_complete_resolution
    • First observedknowbase_diagnose
    • First observedknowbase_lookup
    • First observedknowbase_recall
    • First observedknowbase_register
    • First observedknowbase_report
    • First observedknowbase_report_outcome
    • First observedknowbase_retract
    • First observedknowbase_rotate_secret

Related MCP Connectors

Related MCP Servers

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.