Skip to main content
Glama
Sign In

SVTR AI Venture Database

by ai.svtr
OverviewDiscussionsAdmin

Recent AI Funding Events

get_recent_funding_events
Read-only

最近 7 天有公开来源的 AI 融资事件（公开档位时间窗），可按赛道/行业主题标签/阶段/公司名等单一维度筛选。Sourced AI funding events from the last 7 days (public-tier window), filterable by one dimension (sector, industry topic tag such as AI4S, stage, company, country, year).

Input Schema

NameRequiredDescriptionDefault
tagNoSVTR industry topic tag of the funded company (e.g. AI4S, 智能体, 人形机器人; see svtr.ai/orgs). Narrower than sector.
langNoOutput language, default zh (Chinese).
yearNoFilter by announced year.
stageNoNormalized funding stage. English names (e.g. Seed, Series A) are also accepted.
sectorNoSVTR standard sector. English names (e.g. Robotics, Life Sciences) are also accepted.
companyNoCompany name filter.
countryNoHQ country: Chinese name (美国), English name (United States) or ISO code (US).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / country / description
      Previous value: -"HQ country (Chinese name, e.g. 美国/中国)."New value: +"HQ country: Chinese name (美国), English name (United States) or ISO code (US)."
    • changedInput schema / properties / sector / description
      Previous value: -"SVTR standard sector (26 values)."New value: +"SVTR standard sector. English names (e.g. Robotics, Life Sciences) are also accepted."
    • changedInput schema / properties / stage / description
      Previous value: -"Normalized funding stage."New value: +"Normalized funding stage. English names (e.g. Seed, Series A) are also accepted."
    • addedInput schema / properties / tag
      Added value: +{
+  "description": "SVTR industry topic tag of the funded company (e.g. AI4S, 智能体, 人形机器人; see svtr.ai/orgs). Narrower than sector.",
+  "type": "string"
+}
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare read-only, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely useful behavioral context — the 7-day window boundary and the 'public-tier' source restriction — but says nothing about result ordering, volume, or pagination behavior for what is presumably a feed.

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 parallel sentences, one per language, with the time window and the single-dimension constraint front-loaded. The bilingual duplication is justified because a lang parameter exists and the audience is bilingual; each sentence still carries the scope plus filter list.

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 7-optional-parameter list tool with no output schema, the definition covers selection well but omits anything about the returned record shape, expected result count, or whether an empty window yields an empty list. An agent can call it correctly, but cannot predict what comes back.

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% and enums are documented, so the schema carries most parameter meaning. The description nonetheless adds a non-obvious constraint that filters apply along a 'single dimension' — i.e. these filters are not meant to be combined — which is not derivable from the schema and materially changes how an agent would call the tool.

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?

The description gives a specific verb+resource+scope: 'AI funding events from the last 7 days (public-tier window)'. The 7-day recency window and 'public source' qualifier make it distinguishable from get_sector_landscape or search_organizations. It stops short of naming a sibling as the alternative for broader/older queries.

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 implied by the scoping ('last 7 days', public-tier), so an agent can infer this is the recency feed rather than a general search. However, there is no explicit when-not guidance and no named alternative for older events or multi-filter exploration, so the agent must infer routing from sibling names.

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

All SVTR AI Venture Database toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources