Skip to main content
Glama

Koskamo

by com.koskamo
OverviewDiscussionsAdmin

Find an MCP server

koskamo_find_mcp_server
Read-onlyIdempotent

Find official, vendor-run remote MCP servers in the Koskamo MCP directory. Every listed endpoint passed a recent live check; returns the endpoint URL, sign-in type, documentation link, and known tools.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
authNoOptional sign-in filter; none means usable without an account; oauth-optional means public tools work anonymously and account tools prompt OAuth sign-in
queryNoWords to match against name, operator, description, use cases, and tool names
categoryNoOptional category filter

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
serversYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / servers / items / properties / requirements
      Added value: +{
+  "description": "Accounts, subscriptions, or keys needed before the server is useful",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
  2. Changed3 schema fields changed
    • changedInput schema / properties / category / enum
      Previous value: -[
-  "docs-reference",
-  "developer-tools",
-  "cloud-infrastructure",
-  "data-analytics",
-  "ai-ml",
-  "payments-commerce",
-  "productivity",
-  "project-management",
-  "crm-marketing",
-  "design"
-]New value: +[
+  "docs-reference",
+  "developer-tools",
+  "cloud-infrastructure",
+  "data-analytics",
+  "ai-ml",
+  "commerce",
+  "payments",
+  "productivity",
+  "project-management",
+  "crm-marketing",
+  "design"
+]
    • changedOutput schema / properties / servers / items / properties / category / enum
      Previous value: -[
-  "docs-reference",
-  "developer-tools",
-  "cloud-infrastructure",
-  "data-analytics",
-  "ai-ml",
-  "payments-commerce",
-  "productivity",
-  "project-management",
-  "crm-marketing",
-  "design"
-]New value: +[
+  "docs-reference",
+  "developer-tools",
+  "cloud-infrastructure",
+  "data-analytics",
+  "ai-ml",
+  "commerce",
+  "payments",
+  "productivity",
+  "project-management",
+  "crm-marketing",
+  "design"
+]
    • addedOutput schema / properties / servers / items / properties / companyUrl
      Added value: +{
+  "description": "Company website",
+  "format": "uri",
+  "type": "string"
+}
  3. Changed3 schema fields changed
    • changedInput schema / properties / auth / description
      Previous value: -"Optional sign-in filter; none means usable without an account"New value: +"Optional sign-in filter; none means usable without an account; oauth-optional means public tools work anonymously and account tools prompt OAuth sign-in"
    • changedInput schema / properties / auth / enum
      Previous value: -[
-  "none",
-  "oauth",
-  "api-key"
-]New value: +[
+  "none",
+  "oauth-optional",
+  "oauth",
+  "api-key"
+]
    • changedOutput schema / properties / servers / items / properties / auth / enum
      Previous value: -[
-  "none",
-  "oauth",
-  "api-key"
-]New value: +[
+  "none",
+  "oauth-optional",
+  "oauth",
+  "api-key"
+]
  4. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so safety is covered. The description adds real value beyond that: it discloses that every endpoint passed a recent live check (freshness/validation guarantee) and enumerates what is returned (endpoint URL, sign-in type, docs link, known tools).

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

Conciseness5/5

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

Two tight sentences with no waste. Scope and freshness guarantee are front-loaded, and return contents follow immediately.

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?

An output schema exists, so return values need not be re-explained, and annotations cover the safety profile. The description supplies scope, freshness, and result contents, leaving little an agent would need beyond the schema.

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% with two enum filters fully documented, so the schema carries parameter meaning. The description adds nothing about the query/auth/category parameters, so the baseline 3 is appropriate.

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?

States a specific verb (find) plus resource (remote MCP servers) and constrains scope tightly: official, vendor-run, remote, and within the Koskamo directory. This clearly separates it from sibling koskamo_register_mcp_server (which adds servers rather than locating them).

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

Usage Guidelines3/5

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

The scope hints at when it applies (discovering existing vendor-run servers), but there is no explicit when-to-use/when-not-to-use statement and no alternatives named. Usage is implied rather than spelled out.

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

All Koskamo toolsInspect
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