Skip to main content
Glama

Search Startups

search_startups
Read-onlyIdempotent

Search tracked startups by sector, city, or keyword.

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

Input Schema

NameRequiredDescriptionDefault
queryNoSearch keywords matching a sector, city, or startup name, e.g. fintech, Berlin.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / query / description
      Added value: +"Search keywords matching a sector, city, or startup name, e.g. fintech, Berlin."
    • addedInput schema / properties / query / examples
      Added value: +[
      +  "fintech",
      +  "Berlin",
      +  "devtools"
      +]
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world, and non-destructive, so the safety profile is covered. The description adds one useful scoping fact — results are limited to 'tracked' startups — but says nothing about matching semantics (substring vs exact), result limits, or what an empty/generic query returns.

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 verb and resource, and every clause carries information. No filler or restatement of the title.

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 optional-parameter read tool with full annotation coverage and no output schema, this is close to sufficient. The remaining gap is behavioral detail on matching and result set size, which an agent would want when results look off.

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 'query' parameter already documents sector/city/name matching with examples. The description merely restates the same three categories, adding no format or matching-behavior 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?

States a specific verb (search) and resource (tracked startups) plus the filter dimensions, so the agent knows exactly what it retrieves. It does not explicitly distinguish itself from get_startup_signal, which is the main reason it falls short of a 5.

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?

Usage is only implied — 'search ... by sector, city, or keyword' suggests discovery/browsing, but there is no statement of when to prefer get_startup_signal, list_cities, or list_sectors, nor any exclusions. Adequate for a simple lookup tool but leaves routing to inference.

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