Mode VC Chart: Open-Source vs. Closed AI Models: How Big Is the Gap?

Search the Chart of the Day Archive

search_charts

Read-onlyIdempotent

Searches every chart in the Mode VC Chart of the Day archive by keyword over title, claim, takeaway and keywords. Returns claims, takeaways, canonical URLs, markdown endpoints and cited sources. The archive grows by one chart a day; the response states its current size.

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

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum charts to return. Default 10.
`query`	No	Search term, e.g. "pricing", "claude", "inference", "sdk"

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 21, 2026

removedInput schema / properties / limit / default
```
Removed value: -10
```

changedInput schema / properties / limit / description

Previous value: -"Maximum number of charts to return"New value: +"Maximum charts to return. Default 10."

changedInput schema / properties / limit / maximum
```
Previous value: -38New value: +100
```

changedInput schema / properties / query / description

Previous value: -"Search term matching title, claim, key takeaway, or keywords (e.g. \"pre-seed\", \"pricing\", \"claude\", \"inference\", \"sdk\")"New value: +"Search term, e.g. \"pricing\", \"claude\", \"inference\", \"sdk\""

First observedOct 18, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world). The description adds genuine context beyond them: what the result contains (claims, takeaways, canonical URLs, markdown endpoints, cited sources) and that the archive grows daily with the response reporting its current size.

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?

Three compact sentences, front-loaded with the action and scope, then return contents, then freshness. No filler and nothing repeated from the structured fields.

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

Completeness5/5

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

For a read-only search tool with no output schema, the description covers scope, matching fields, returned artifacts, and data freshness. An agent has everything needed to call it and interpret the result.

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 the baseline is 3, but the description earns a bump by clarifying what the free-text query actually matches against (title, claim, takeaway, keywords), which the schema alone does not say. The limit parameter is left entirely to 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?

States a specific verb (Searches) and resource (every chart in the Mode VC Chart of the Day archive) plus the exact fields matched (title, claim, takeaway, keywords). The read/search framing implicitly separates it from the get_* siblings, but no sibling is named explicitly, so it stops short of a 5.

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: reach for this when you want to find charts by keyword rather than fetch a known one. However, it never says when to prefer it over get_chart_data or get_venture_chart_of_the_day, and there are no stated exclusions or prerequisites.

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

All Mode VC Chart: Open-Source vs. Closed AI Models: How Big Is the Gap? tools Inspect

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

Need Help?