Skip to main content
Glama

StartupMKT — Startup Discovery & Marketplace

Startups and micro-SaaS for sale

startups_for_sale

Marketplace listings currently open to acquisition on StartupMKT, with asking price where the seller published one.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many listings to return (1-50, default 10).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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 burden, and it does disclose two useful behaviors: results are filtered to currently-open listings, and the asking price is only populated 'where the seller published one' (i.e., a nullable field). It says nothing about ordering, pagination behavior, or that this is a read-only query.

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?

One compact sentence, front-loaded with the resource and scope, with the price caveat appended. Every clause carries information and there is no filler.

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-optional-parameter listing tool with no output schema and no annotations, the description conveys source, filtering scope, and return-content caveat, which is most of what an agent needs. It stops short of describing the fields returned per listing, the only real gap.

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 coverage is 100% and the single 'limit' parameter is fully documented in the schema (range 1-50, default 10). The description adds no syntax or format detail beyond the schema, so the 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?

Names a specific resource and scope: marketplace listings open to acquisition on StartupMKT. A verb is only implied ('returns'), and it does not explicitly distinguish itself from siblings, but those siblings (latest_funding, search_collections) cover clearly different domains.

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

Usage Guidelines2/5

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

No statement of when to use this tool, when not to, or which alternative to pick. Usage is only inferable from the noun phrase 'marketplace listings currently open to acquisition'. No prerequisites or exclusions are given.

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