Skip to main content
Glama

Find an MCP server

koskamo_search_mcp_servers
Read-onlyIdempotent

Find remote MCP servers and local MCP packages. Filter by vendor/community publisher, transport, capabilities, and sign-in. Live-check and source-verification states are returned independently.

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": "koskamo_search_mcp_servers"
  }
}

Input Schema

NameRequiredDescriptionDefault
authNoOptional remote sign-in filter
kindNoRemote endpoint or local package
limitNoMaximum rows in this page
queryNoWords to match against name, operator, description, use cases, requirements, and capability descriptions
offsetNoContinue from pagination.nextOffset while keeping the same filters
behaviorNoMatch explicit server-advertised annotations only
categoryNoOptional category filter
publisherNoWhether the publisher is the vendor or a community maintainer
transportNoTransport supported by the server or package
capabilityNoCapability the listing must advertise

Output Schema

NameRequiredDescriptionDefault
serversYes
paginationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered structurally. The description adds one genuinely non-obvious detail — that live-check and source-verification states are returned independently — but does not address indexing freshness, rate limits, or result ordering.

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?

Two short sentences, front-loaded with the core purpose and followed by the filter/behavior note; zero filler. The final clause about independent live-check and verification states is slightly compressed and could be misread, but it earns its place.

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?

With an output schema and full annotation set present, the description needn't explain returns or safety. It covers the search scope and the filterable axes for a 10-parameter, all-optional search tool; only guidance on choosing between this and sibling lookup tools is missing.

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 seven enums documented inline, so the schema already carries the parameter burden. The description only echoes a subset of filters (publisher, transport, capabilities, sign-in) without adding syntax or semantics beyond the schema. Baseline 3 applies.

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?

States a specific verb and resource — "Find remote MCP servers and local MCP packages" — which distinguishes it from the singular retrieval sibling koskamo_get_mcp_server. It also enumerates the filterable dimensions, so an agent knows this is a discovery/search tool rather than a lookup. It stops short of naming an alternative explicitly.

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 filter list implies a discovery workflow (use when you don't yet know which server you want), but there is no explicit when-to-use statement, no exclusion, and no mention of when to prefer koskamo_get_mcp_server or koskamo_search_use_cases instead. Usage must be inferred from the parameter surface.

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