Skip to main content
Glama

StartupMKT — Startup Discovery & Marketplace

Search StartupMKT collections

search_collections

Search StartupMKT curated collection pages (e.g. "Top 25 AI Agents", "Startups over $10k MRR"). Returns matching collections that actually have listings, with title, URL and item count.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_collections"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesTopic to search for, e.g. "ai agents", "crm software", "profitable startups".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 add a genuine behavior disclosure — results are limited to collections that 'actually have listings' — and names the return fields (title, URL, item count). However, it says nothing about auth requirements, result limits, pagination, or matching semantics.

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 filler. The core action and scope lead, and the return contract follows, so the agent gets the essentials 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?

For a single-parameter search with no output schema and no annotations, the description covers purpose, the result-filtering rule, and returned fields — enough to invoke it correctly. It stops short of pagination/result-limit behavior, which an agent might need for broad queries.

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 documents itself with examples ('ai agents', 'crm software'), so the schema does the heavy lifting. The description's collection examples illustrate the domain but add no new syntax or format meaning for the parameter.

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 (Search) and resource (StartupMKT curated collection pages), with concrete examples of what a collection looks like. It is clearly distinguishable from the sibling get_collection, which retrieves one collection rather than searching across 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 word 'Search' against curated collection pages implies the usage context, and the contrast with get_collection is inferable, but the description never says when to prefer this over get_collection or the other sibling tools. No prerequisites or exclusions are stated.

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