Skip to main content
Glama

Apex Portfolio Match

apex_portfolio_match
Read-onlyIdempotent

Match your project idea to the most relevant Apex portfolio companies. Get ranked results with similarity scores and insights to identify potential reference customers or check thesis overlap.

Instructions

Find Apex portfolio projects most similar to the founder's idea or company description. Returns a ranked list with similarity scores, a one-sentence rationale (whyMatch) and a short founder-applicable lesson (shortLesson) for each match. Use this to surface which Apex portfolio companies are closest to a project the founder is asking about, identify potential reference customers, or check thesis overlap before pitching Apex.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
descriptionYesThe project or idea to match against the Apex portfolio. 40-5000 chars. Concrete and specific produces better matches than vague descriptions.
categoryNoOptional category tag for the project (e.g. "DeFi", "RWA", "Infrastructure", "Privacy"). Used as a soft signal when ranking.
tagsNoOptional free-form tags (max 20). Used as soft ranking signals.
stageNoOptional stage filter. Lets the engine prefer matches at a similar maturity.
tokenStatusNoOptional token status filter.
topNNoMax number of matches to return (1-10, default 5).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYes
matchesYesTop portfolio matches, ranked by similarity descending.
summaryYes
Behavior4/5

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

Annotations indicate readOnly, idempotent, non-destructive. Description adds return details (scores, whyMatch, shortLesson) and hints at matching behavior. No contradictions.

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?

Four sentences, each essential. Front-loaded with action, then returns, then use cases. No wasted words.

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?

Covers purpose, use cases, and param hints. Output schema exists, so return details are handled. With 6 params and 1 required, description is sufficiently complete.

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

Parameters4/5

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

Schema coverage is 100%, so description adds limited param detail. However, it provides extra context for the `description` parameter (concrete/specific yields better matches), improving semantics beyond schema.

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

Purpose5/5

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

The description clearly states the tool finds Apex portfolio projects similar to a founder's idea, returns a ranked list with similarity scores, rationale, and lesson. It distinguishes from siblings like apex_fund_match by focusing on portfolio matching.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit use cases: surface closest projects, identify reference customers, check thesis overlap. Lacks 'when not to use' or alternatives, but context is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Apex-Foundation/copilot-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server