Skip to main content
Glama

StartupMKT — Startup Discovery & Marketplace

Get a StartupMKT collection

get_collection

Get the top items in one StartupMKT collection by slug (from search_collections): startup names, one-line descriptions and StartupMKT URLs.

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": {
      "slug": "<slug>"
    },
    "name": "get_collection"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesCollection slug, e.g. "top-25-ai-agents".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the behavioral burden. It discloses the shape of the result ('top items', name/description/URL) but says nothing about how 'top' is defined, result limits, ordering, or error behavior for a bad slug. Adequate but thin for a tool with zero annotation coverage.

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 sentence, front-loaded with the action and the key constraint (one collection by slug), and every clause carries information. 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 single-parameter read tool with no output schema, the description covers what is fetched and what comes back. Missing only limits/ordering detail and failure behavior, which are minor for 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 coverage is 100% and the property already documents the slug format with an example. The description adds the provenance of the slug (search_collections), but no additional syntax or constraints beyond the schema — baseline 3 is correct.

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 (Get) and resource (top items in one collection) and names the return fields (startup names, one-line descriptions, StartupMKT URLs). It also anchors the identifier's origin to search_collections, separating it from siblings like about or latest_funding.

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 parenthetical 'slug (from search_collections)' tells the agent this tool is the step after search_collections, which is real routing guidance. It stops short of stating when not to use it or what happens for an unknown/slugless collection.

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