Skip to main content
Glama

Get an investor

naut_get_investor
Read-only

One fund with its team and portfolio. Costs 5 credits.

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

Input Schema

NameRequiredDescriptionDefault
slugYesInvestor slug or id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/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 the safety profile is covered. The description contributes genuinely new behavioral information: the 5-credit cost and the fact that the response bundles team and portfolio data. It does not cover error behavior for an unknown slug or any rate/limit context.

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 short sentences with no filler, and the return scope is front-loaded ahead of the cost note. The phrasing "One fund with its team and portfolio" is slightly fragmentary and leaves the action implicit, which keeps it from a 5.

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 single-record getter with no output schema, the description gives only a high-level hint of the return contents (team and portfolio) and no structural detail. It is roughly adequate for a one-parameter read, but an agent cannot anticipate the response shape or cost implications beyond the single credit figure.

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 'slug' parameter is already documented as 'Investor slug or id.' The description adds nothing about slug format, accepted id forms, or what happens on a miss, so it does not go beyond the schema. Baseline 3 applies given the complete schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says what comes back ("One fund with its team and portfolio") which identifies this as a single-investor detail fetch, but it omits an explicit verb and never distinguishes itself from naut_search_investors or the other naut_get_* siblings. An agent can mostly infer the purpose but must rely on the tool name for the verb.

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 guidance and no reference to alternatives such as naut_search_investors for lookup versus this tool for detail retrieval. The only guidance-adjacent content is the credit cost, which is useful for budgeting but does not tell an agent when to select this tool over a sibling.

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