TrendIdea

get_investment_memo

Read-only

Return a VC-style investment memo for an idea: thesis, key risks, comparable exits and a clear recommendation. Use it to present an idea to investors or to pressure-test your own conviction. Read-only and free; pass an ideaId you own that has been validated.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`ideaId`	Yes	The idea ID

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes	The tool result rendered as human and AI readable text or markdown.

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false. Description adds that it is 'Read-only and free', which reinforces safe behavior. It also clarifies the data source (validated ideas) and that the output includes specific sections.

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?

Two sentences: first defines purpose and content, second explains use cases and constraints. Every word adds value, no fluff, front-loaded with key information.

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?

Given the tool has output schema (not shown) and only 1 simple parameter, the description adequately covers purpose, prerequisites, and behavioral traits. Slight gap: no mention of what happens with invalid or unvalidated ideaId, but overall sufficient.

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% with a clear description for ideaId. The description adds context about the idea needing to be validated and owned by the user, which goes beyond the schema's 'The idea ID' but the parameter semantics are minimal and schema already handles it.

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?

Description specifies verb 'return', resource 'VC-style investment memo', and content (thesis, key risks, comparable exits, recommendation). It clearly distinguishes tasks like generating pitches (generate_b2b_pitch) or summaries (get_idea_summary).

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

Usage Guidelines5/5

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

Explicitly states when to use: 'present an idea to investors or to pressure-test your own conviction'. Also provides prerequisite: 'pass an ideaId you own that has been validated', which improves usage guidance.

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

All TrendIdea tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0

Disambiguation5/5

Each tool targets a distinct function or data aspect, from idea CRUD to simulations, content generation, and team management. Despite the large number, descriptions clearly differentiate purposes, e.g., 'get_idea_summary' vs. 'get_idea_agents' vs. 'get_idea_evolution'. No two tools appear to do the same thing.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern in snake_case (e.g., 'create_idea', 'get_competitive_density', 'toggle_favorite'). No mixing of conventions like camelCase or abbreviations. The pattern is uniform and predictable.

Tool Count2/5

63 tools is far beyond the typical well-scoped range of 3-15. While the platform's broad scope (idea validation, B2B, team, simulations) justifies many, the sheer volume can overwhelm an agent. A more curated subset or grouping would improve coherence.

Completeness5/5

The tool set covers the full startup idea lifecycle: creation, validation, retrieval of various analyses, updates, deletion, sharing, simulations, B2B lead generation, team collaboration, and market intelligence. No obvious gaps exist for the stated domain.

Resources

Need Help?