Skip to main content
Glama

List recent Founder Ventures intel

list_intel
Read-onlyIdempotent

Recent intel posts: short, dated reads of one event in the bootstrapped and product-led SaaS market (funding, pricing changes, launches, research). Newest first. Read one in full with read_founder_ventures_page.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
categoryNo

Output Schema

NameRequiredDescriptionDefault
postsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, closed-world, non-destructive, so the safety profile is covered. The description adds ordering (newest first) and the content shape, which is genuine value. It does not address pagination, whether limit caps the total, or any rate limits.

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 tight sentences, front-loaded with resource and content shape, then ordering, then the drill-down routing. No filler or restated name/title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be described. But with 0% schema coverage on both parameters and a listing tool where limit semantics matter, the description leaves real gaps: what limit controls and how category narrows results are both unexplained.

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 0%, so the description must compensate. 'Recent' and 'Newest first' imply the limit's effect, and the listed content types (funding, pricing changes, launches, research) loosely map to the category enum, but the enum literals market-shift, tool-launch and competitive-move are not explicitly explained and the limit's default/max are unstated. Partial compensation only.

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 (list) and resource (recent intel posts) and characterizes the content precisely: short, dated reads of one event in the bootstrapped and product-led SaaS market. That is enough to distinguish it from read_founder_ventures_page, though it never names search_founder_ventures as the alternative.

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?

Implies a browse-recent use case and explicitly routes the agent to read_founder_ventures_page for full reads, which is useful. However there is no explicit when-not or when-to-use-this-vs-search_founder_ventures guidance.

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