Skip to main content
Glama

BetaList startups search

run_betalist_startups_search
Read-onlyIdempotent

Search BetaList startups by keyword: name, tagline, logo and link. 1 point per returned record.

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": {
      "keyword": "<keyword>"
    },
    "name": "run_betalist_startups_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordYesKeyword. e.g. ai
max_itemsNoMax items (up to 250) Default: 25.
start_pageNoStarting page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 the safety profile is covered. The description adds genuinely new context beyond that: the credit cost ('1 point per returned record') and the shape of the returned fields (name, tagline, logo, link), which is real value not present in the annotations.

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 compact clauses with no wasted words; the search scope is front-loaded and the cost note is appended efficiently. Slightly terse phrasing ('by keyword: name, tagline, logo and link') leaves the relationship between keyword and returned fields implicit, but nothing is padded.

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 no output schema, the description helpfully enumerates the returned fields and discloses the per-record cost. It does not mention pagination behavior despite the start_page parameter, which is a minor gap for a paginated search tool, but overall it covers what an agent needs.

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 keyword, max_items (up to 250, default 25), and start_page all documented in the schema. The description adds no additional parameter semantics beyond what the schema already provides, 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?

States a specific verb (search) and resource (BetaList startups), scoped by keyword, and names the fields returned (name, tagline, logo, link). The 'by keyword' phrasing loosely separates it from the non-search siblings, but it never names run_betalist_startups, run_betalist_startups_latest, or run_betalist_topics_startups to make the distinction explicit.

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?

The description implies a keyword-search use case but gives no when-to-use guidance and no exclusions relative to its close siblings (the plain list, latest, and topics variants). An agent must infer from the tool name alone which of the four BetaList tools to pick.

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