Skip to main content
Glama

Investor profile

investor_profile
Read-only

A crypto investor's public profile (type, location, website, industries, investment criteria) and its investments, newest first, 50 per page. Free data from AlphaGrowth (alphagrowth.io).

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number of the investments, 50 per page.
slugYesThe investor's slug or name (e.g. polychain-capital, Polychain Capital); top_investors and recent_funding_rounds list them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / slug / description
      Previous value: -"The investor's slug; find it with top_investors or recent_funding_rounds."New value: +"The investor's slug or name (e.g. polychain-capital, Polychain Capital); top_investors and recent_funding_rounds list them."
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavior beyond that: results are ordered newest first, paginated at 50 per page, and sourced free from AlphaGrowth. It omits what happens on an unknown slug or whether page bounds are clamped.

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 front-loaded sentence that packs the field list, ordering and page size without filler; the data-source attribution is a mild extra but not wasteful. Nothing needs trimming for comprehension.

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 read-only single-investor lookup with full schema coverage and no output schema, the description compensates by enumerating the returned profile fields and the investments ordering. Only the failure behavior for a missing slug is unaddressed.

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%, so both parameters are already documented, including the page minimum/maximum and slug examples. The description reinforces the page semantics ('50 per page') and the slug concept but adds no format or syntax detail beyond the schema.

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?

Names a specific resource (a crypto investor's public profile plus its investments) and enumerates the fields returned, so an agent knows exactly what it gets. It is distinguishable from top_investors because it resolves one investor by slug, though the description itself never explicitly contrasts the two.

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: you need a slug or name to call it, and the slug parameter description points to top_investors and recent_funding_rounds as the places those come from. There is no explicit statement of when to prefer this over listing-oriented siblings or what to do when the slug is unknown.

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