Skip to main content
Glama

Search investors

naut_search_investors
Read-only

Search and filter funds. Supports q, fundType, trustTier, sort. Costs 5 credits.

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

Input Schema

NameRequiredDescriptionDefault
qNoText to match against names, handles and domains.
pageNoPage number, from 1.
sortNo
limitNoRows per page, 1 to 100. Default 30.
fundTypeNo
trustTierNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description does add genuinely useful non-schema behavior: a fixed cost of 5 credits per call. It omits pagination behavior and what the result set contains.

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?

Three short sentences, front-loaded with the purpose and ending with the cost, with no wasted prose. The middle sentence is a bare parameter list that partly duplicates the schema.

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 read-only search tool with six optional parameters and no output schema, the definition is serviceable but thin. It leaves the two undocumented enum-like filters (fundType, trustTier) undefined and says nothing about what is returned or how sorting modes behave.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 50%; q, page, and limit are documented in the schema, but fundType and trustTier have no descriptions anywhere. The description merely repeats those parameter names in a bare list without explaining accepted values, matching rules, or the meaning of trust tiers, so it does not compensate for the gap.

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 and resource ('Search and filter funds') with the filter dimensions enumerated. It does not distinguish itself from the many sibling search tools (naut_search, naut_search_people, naut_search_projects), and the resource is named 'funds' while the tool is named 'investors', which slightly muddies targeting.

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 explicit when-to-use or when-not guidance, and no alternative tools are named. The agent must infer from the name alone that this is the investor-specific variant of the generic search.

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