Skip to main content
Glama

Mode VC Chart: Ollama Downloads: Is Local LLM Adoption Keeping Up?

Latest Charts from the Mode VC Chart of the Day

get_venture_chart_of_the_day
Read-onlyIdempotent

Returns the most recent charts from Mode VC's Chart of the Day archive (one new chart per day, mostly AI model, adoption, developer-package and pricing data), newest first, each with its claim, takeaway, URL and cited sources.

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

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of recent charts. Default 3.

Output Schema

NameRequiredDescriptionDefault
as_ofNo
provenanceYes
source_urlsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "as_of": {
      +      "type": "string"
      +    },
      +    "provenance": {
      +      "properties": {
      +        "as_of": {
      +          "type": "string"
      +        },
      +        "as_of_basis": {
      +          "type": "string"
      +        },
      +        "sources": {
      +          "items": {
      +            "type": "object"
      +          },
      +          "type": "array"
      +        }
      +      },
      +      "required": [
      +        "as_of",
      +        "as_of_basis",
      +        "sources"
      +      ],
      +      "type": "object"
      +    },
      +    "source_urls": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "provenance"
      +  ],
      +  "type": "object"
      +}
  2. Changed2 schema fields changed
    • removedInput schema / properties / limit / default
      Removed value: -3
    • changedInput schema / properties / limit / description
      Previous value: -"Number of recent charts to retrieve"New value: +"Number of recent charts. Default 3."
  3. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds context the annotations do not: a fixed one-chart-per-day publication cadence, newest-first ordering, and the nature of the underlying dataset. With an output schema present, it does not need to enumerate return fields exhaustively.

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?

One front-loaded sentence with the resource and scope stated first, followed by qualifying detail. The parenthetical about content type is dense but earns its place by telling the agent what kind of data to expect, and there is no redundant restatement of the title or schema.

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?

This is a simple read-only retrieval tool with one optional parameter, full schema coverage and an output schema that documents return values. The description covers source, cadence, ordering and content domain, which is everything needed to call it correctly; no behavioral or return-format details are missing at this complexity level.

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 description coverage is 100% for the single 'limit' parameter, including minimum, maximum and default, so the schema carries the semantics. The description only alludes to it via 'most recent charts' and adds no guidance on choosing a limit or on behavior when the archive has fewer entries than requested. Baseline 3 is appropriate.

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 ('Returns'), a specific resource ('the most recent charts from Mode VC's Chart of the Day archive'), and the domain of content ('AI model, adoption, developer-package and pricing data'). It implicitly separates itself from search-style siblings by stating 'newest first' and 'most recent', but it never names search_charts or get_chart_data as the alternative, so the differentiation is inferred rather than explicit.

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 only implied: the words 'most recent' and 'latest' signal when this tool applies, and 'one new chart per day' hints at what it is not for (deeper or historical retrieval). There is no explicit statement of when to prefer it over the sibling chart tools, and no exclusions or prerequisites.

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