Skip to main content
Glama

run_techeu_investors_search

Search Tech.eu's investor directory by name, type, deal count, portfolio companies, sector, or active years to find and compare investors.

Instructions

Search the Tech.eu investor directory by name: type, number of deals and companies, top sector and active years. 1 point per returned record.

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

Input Schema

NameRequiredDescriptionDefault
sortNoSort by. Options: deals_desc = Most deals, companies_desc = Most companies, name = Name
typeNoType (e.g. Venture capital). e.g. Venture capital
keywordNoInvestor name. e.g. sequoia
max_itemsNoMax items (up to 250)
start_pageNoStarting page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

B3.2/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 does partly compensate by disclosing the per-record cost ('1 point per returned record') and the fields returned (deals, companies, sector, active years), which substitutes for the absent output schema. However it says nothing about pagination behavior, result limits, or any auth/rate-limit constraints.

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?

A single compact sentence plus a short cost clause; the purpose is front-loaded and there is no filler. Slightly dense because it mixes searchable criteria with returned fields, but efficiently sized.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 5-parameter, no-annotation, no-output-schema tool the description does cover the returned field set, which is helpful. It still omits how to page through large result sets and when to prefer the sibling investor tools, so it is adequate but not complete.

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%, so every parameter is already documented in the schema (sort enum, type, keyword, max_items, start_page). The description only echoes 'by name' for keyword and adds nothing about the sort, paging, or type semantics, so the baseline 3 is correct.

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 clear verb (Search) and a specific resource (the Tech.eu investor directory) and lists the fields exposed (deals, companies, sector, active years). It does not distinguish itself from the sibling run_techeu_investors (the non-search lister) or from the many other *_investors_search tools, so sibling differentiation is missing.

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?

There is no when-to-use or when-not-to-use guidance and no mention of alternatives such as run_techeu_investors or run_eustartups_investors_search. 'By name' hints that keyword is the intended selector, but usage is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools