Skip to main content
Glama
Sign In

knowledge

by at.designare
OverviewDiscussionsAdmin

Server Details

Knowledge Base von designare.at – Michael Kanda, Web & KI aus Wien. Semantische Suche über RAG.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over 78 days
Last Tested
Transport
Streamable HTTP · MCP 2025-03-26
URL
Repository
michael-kanda/designare
GitHub Stars
0
ChatGPT
–
Claude
–

TDQS

A3.8/5.0

Scored across 2 tools

Disambiguation4/5

get_services returns a fixed, canonical competence profile, while search_knowledge performs semantic retrieval across the knowledge base. The purposes are mostly distinct, though both can answer overlapping questions about Michael Kanda/designare.at, so an agent might occasionally choose search when the profile tool would be more direct.

Naming Consistency5/5

Both tools follow a clear verb_noun snake_case pattern: get_services and search_knowledge. The legacy name get_services is explicitly explained in the description, so it does not break predictability.

Tool Count3/5

Two tools is thin for a knowledge server, even a narrow one. The surface is coherent, but additional operations such as listing articles or fetching a specific page could reasonably earn a place.

Completeness4/5

The server covers the core read-only needs: retrieving the canonical profile and searching the knowledge base semantically. Minor gaps exist, such as direct retrieval by page slug or listing all articles/projects, but search largely compensates for these.

Available Tools

2 tools
get_servicesA
Read-onlyIdempotent
Inspect

Liefert das belegbare Kompetenz- und Projektprofil von Michael Kanda / designare.at: Person, Fachfelder, typische Aufgaben, Ergebnisse, Produkte, Open-Source-Werkzeuge und kanonische Belegseiten. Der technische Tool-Name bleibt aus Kompatibilitätsgründen get_services. Nutze das Tool für Fragen wie "Was macht designare.at?" oder "Welche Projekte und Fachgebiete hat Michael Kanda?".

NameRequiredDescriptionDefault

No parameters

Output Schema

NameRequiredDescription
productsYes
providerYes
provenanceYes
lastUpdatedYes
schemaVersionYes
competenceAreasYes
openSourceToolsYes

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive, closed-world operation, so the description does not need to repeat safety semantics. It adds useful behavioral context by specifying the profile content and canonical evidence pages, though it does not discuss output format or any access constraints.

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?

The description is front-loaded with what the tool returns, then gives example use cases, with a brief compatibility note about the technical name. It is appropriately sized for a no-parameter tool, though the compatibility sentence is slightly meta and could be trimmed.

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?

Given the empty input schema, rich annotations, and the presence of an output schema, the description is nearly complete: it explains the content and typical questions. The main missing context is sibling routing, since an agent may also consider search_knowledge for related queries.

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

Parameters4/5

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

The tool has zero parameters, so the baseline is 4. The description correctly does not invent parameter semantics, and the empty schema is consistent with a parameterless profile retrieval tool.

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

Purpose4/5

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

The description clearly states the tool returns a specific resource: the verifiable competence and project profile of Michael Kanda / designare.at, including person, fields, tasks, results, products, open-source tools, and evidence pages. It also explains the otherwise misleading technical name, but it does not explicitly distinguish this tool from the sibling search_knowledge.

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?

The description gives concrete example questions that should trigger this tool, such as 'Was macht designare.at?' and 'Welche Projekte und Fachgebiete hat Michael Kanda?'. It does not state when to use search_knowledge instead or provide exclusions, so it is clear but not fully routing-aware.

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

search_knowledgeAInspect

Semantische Suche in der designare.at Knowledge Base. Findet relevante Informationen über Michael Kanda, seine Web- und KI-Kompetenzfelder, Projekte, Blog-Artikel und Expertise. Nutze dieses Tool wenn du Fragen über designare.at, WordPress, SEO, GEO (Generative Engine Optimization), KI-Sichtbarkeit oder Michael Kandas Arbeit beantworten willst.

NameRequiredDescriptionDefault
queryYesDie Suchanfrage in natürlicher Sprache (deutsch oder englisch). Beispiele: "Womit beschäftigt sich Michael Kanda?", "Was ist GEO?", "Welche WordPress-Projekte gibt es?"

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden; it does disclose that retrieval is semantic rather than keyword-based, which is genuinely useful context for query phrasing. It says nothing about result volume, ranking behavior, latency, or whether the corpus is read-only, leaving the mutation/return profile to inference.

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 the core purpose before the usage trigger, with essentially no filler. The topic enumeration is slightly listy but each item helps an agent decide whether to route here.

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 one-parameter, non-destructive lookup with no output schema, the description covers purpose, corpus scope, and when to invoke it. The remaining gap is the boundary with get_services and any hint about result shape, which is minor at this complexity.

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

Parameters3/5

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

Schema description coverage is 100% and the single `query` parameter already carries language guidance and three worked examples, so the schema does the heavy lifting. The description adds topical context about what queries will hit but no additional syntax, scope, or format guidance beyond the schema.

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

Purpose4/5

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

The description names a specific verb+resource pair ("Semantische Suche in der designare.at Knowledge Base") and enumerates the content domains covered (projects, blog articles, expertise). It does not explicitly distinguish itself from the sibling get_services, so an agent must infer the boundary rather than being told it.

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?

"Nutze dieses Tool wenn du Fragen über ... beantworten willst" gives a concrete, topic-level trigger list (designare.at, WordPress, SEO, GEO, KI-Sichtbarkeit), which is clear positive guidance. No exclusions or named alternatives are given, so the agent has no stated rule for when to prefer the sibling instead.

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

Tool Schema Changelog

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

  1. 1 tool update
    • Changedget_services7 fields changed
      • addedOutput schema / properties / competenceAreas
        Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "description": {
+        "type": "string"
+      },
+      "evidenceUrls": {
+        "items": {
+          "format": "uri",
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "id": {
+        "type": "string"
+      },
+      "name": {
+        "type": "string"
+      },
+      "outcomes": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "problemsSolved": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "relevantFor": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "url": {
+        "format": "uri",
+        "type": "string"
+      }
+    },
+    "required": [
+      "id",
+      "name",
+      "description",
+      "url",
+      "relevantFor",
+      "problemsSolved",
+      "outcomes",
+      "evidenceUrls"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
      • removedOutput schema / properties / provider / properties / areaServed
        Removed value: -{
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}
      • addedOutput schema / properties / provider / properties / geographicContext
        Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
      • addedOutput schema / properties / provider / properties / scopeNote
        Added value: +{
+  "type": "string"
+}
      • changedOutput schema / properties / provider / required
        Previous value: -[
-  "type",
-  "name",
-  "profileType",
-  "professionalRole",
-  "tagline",
-  "profileUrl",
-  "brand",
-  "location",
-  "areaServed",
-  "languages",
-  "contactUrl",
-  "sameAs"
-]New value: +[
+  "type",
+  "name",
+  "profileType",
+  "scopeNote",
+  "professionalRole",
+  "tagline",
+  "profileUrl",
+  "brand",
+  "location",
+  "geographicContext",
+  "languages",
+  "contactUrl",
+  "sameAs"
+]
      • removedOutput schema / properties / services
        Removed value: -{
-  "items": {
-    "additionalProperties": false,
-    "properties": {
-      "description": {
-        "type": "string"
-      },
-      "evidenceUrls": {
-        "items": {
-          "format": "uri",
-          "type": "string"
-        },
-        "type": "array"
-      },
-      "id": {
-        "type": "string"
-      },
-      "name": {
-        "type": "string"
-      },
-      "outcomes": {
-        "items": {
-          "type": "string"
-        },
-        "type": "array"
-      },
-      "problemsSolved": {
-        "items": {
-          "type": "string"
-        },
-        "type": "array"
-      },
-      "targetAudience": {
-        "items": {
-          "type": "string"
-        },
-        "type": "array"
-      },
-      "url": {
-        "format": "uri",
-        "type": "string"
-      }
-    },
-    "required": [
-      "id",
-      "name",
-      "description",
-      "url",
-      "targetAudience",
-      "problemsSolved",
-      "outcomes",
-      "evidenceUrls"
-    ],
-    "type": "object"
-  },
-  "type": "array"
-}
      • changedOutput schema / required
        Previous value: -[
-  "schemaVersion",
-  "lastUpdated",
-  "provider",
-  "services",
-  "products",
-  "openSourceTools",
-  "provenance"
-]New value: +[
+  "schemaVersion",
+  "lastUpdated",
+  "provider",
+  "competenceAreas",
+  "products",
+  "openSourceTools",
+  "provenance"
+]
  2. 2 tool updates
    • Changedget_services2 fields changed
      • addedOutput schema / properties / provider / properties / profileType
        Added value: +{
+  "type": "string"
+}
      • changedOutput schema / properties / provider / required
        Previous value: -[
-  "type",
-  "name",
-  "professionalRole",
-  "tagline",
-  "profileUrl",
-  "brand",
-  "location",
-  "areaServed",
-  "languages",
-  "contactUrl",
-  "sameAs"
-]New value: +[
+  "type",
+  "name",
+  "profileType",
+  "professionalRole",
+  "tagline",
+  "profileUrl",
+  "brand",
+  "location",
+  "areaServed",
+  "languages",
+  "contactUrl",
+  "sameAs"
+]
    • Changedsearch_knowledge1 field changed
      • changedInput schema / properties / query / description
        Previous value: -"Die Suchanfrage in natürlicher Sprache (deutsch oder englisch). Beispiele: \"Welche SEO-Leistungen bietet designare.at?\", \"Was ist GEO?\", \"Webdesign Wien\""New value: +"Die Suchanfrage in natürlicher Sprache (deutsch oder englisch). Beispiele: \"Womit beschäftigt sich Michael Kanda?\", \"Was ist GEO?\", \"Welche WordPress-Projekte gibt es?\""
  3. 1 tool update
    • Changedget_services2 fields changed
      • addedInput schema / additionalProperties
        Added value: +false
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "lastUpdated": {
+      "format": "date",
+      "type": "string"
+    },
+    "openSourceTools": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "description": {
+            "type": "string"
+          },
+          "evidenceUrl": {
+            "format": "uri",
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "repositoryUrl": {
+            "format": "uri",
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "name",
+          "description",
+          "repositoryUrl",
+          "evidenceUrl"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "products": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "category": {
+            "type": "string"
+          },
+          "description": {
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "status": {
+            "type": "string"
+          },
+          "url": {
+            "format": "uri",
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "name",
+          "category",
+          "description",
+          "url",
+          "status"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "provenance": {
+      "additionalProperties": false,
+      "properties": {
+        "canonicalProfile": {
+          "format": "uri",
+          "type": "string"
+        },
+        "note": {
+          "type": "string"
+        },
+        "source": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "source",
+        "canonicalProfile",
+        "note"
+      ],
+      "type": "object"
+    },
+    "provider": {
+      "additionalProperties": false,
+      "properties": {
+        "areaServed": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "brand": {
+          "additionalProperties": false,
+          "properties": {
+            "name": {
+              "type": "string"
+            },
+            "url": {
+              "format": "uri",
+              "type": "string"
+            }
+          },
+          "required": [
+            "name",
+            "url"
+          ],
+          "type": "object"
+        },
+        "contactUrl": {
+          "format": "uri",
+          "type": "string"
+        },
+        "languages": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "location": {
+          "additionalProperties": false,
+          "properties": {
+            "city": {
+              "type": "string"
+            },
+            "country": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "city",
+            "country"
+          ],
+          "type": "object"
+        },
+        "name": {
+          "type": "string"
+        },
+        "professionalRole": {
+          "type": "string"
+        },
+        "profileUrl": {
+          "format": "uri",
+          "type": "string"
+        },
+        "sameAs": {
+          "items": {
+            "format": "uri",
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "tagline": {
+          "type": "string"
+        },
+        "type": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "type",
+        "name",
+        "professionalRole",
+        "tagline",
+        "profileUrl",
+        "brand",
+        "location",
+        "areaServed",
+        "languages",
+        "contactUrl",
+        "sameAs"
+      ],
+      "type": "object"
+    },
+    "schemaVersion": {
+      "type": "string"
+    },
+    "services": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "description": {
+            "type": "string"
+          },
+          "evidenceUrls": {
+            "items": {
+              "format": "uri",
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "id": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "outcomes": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "problemsSolved": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "targetAudience": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "url": {
+            "format": "uri",
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "name",
+          "description",
+          "url",
+          "targetAudience",
+          "problemsSolved",
+          "outcomes",
+          "evidenceUrls"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "schemaVersion",
+    "lastUpdated",
+    "provider",
+    "services",
+    "products",
+    "openSourceTools",
+    "provenance"
+  ],
+  "type": "object"
+}
  4. 2 tool updates
    • First observedget_services
    • First observedsearch_knowledge

Related MCP Connectors

Related MCP Servers

  • Apple RAG MCP

    adimowis
    F
    license
    Not graded
    quality
    Not graded
    maintenance
    Provides AI agents with instant access to official Apple developer documentation, Swift docs, design guidelines, and Apple Developer YouTube content through advanced semantic and hybrid search capabilities. Features AI-powered reranking for accurate retrieval of Apple platform knowledge including iOS, macOS, watchOS, tvOS, and visionOS development resources.
    5
    -

  • MCP RAG Server

    0xrdan
    A
    license
    Not graded
    quality
    C
    maintenance
    Enables AI assistants to search and retrieve information from your knowledge base using RAG (Retrieval-Augmented Generation) with hybrid search, document indexing, and ChromaDB vector storage.
    29 npm
    MIT

  • micro-app-mcp

    didengren
    A
    license
    Not graded
    quality
    D
    maintenance
    Provides semantic search and knowledge base management for the micro-app micro-frontend framework by ingesting its source code and documentation.
    18
    MIT
Try in Browser
Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources