Skip to main content
Glama

Mode VC Chart: AI Chatbot Adoption by Age: ChatGPT Hits 61% in Youth

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

NameRequiredDescriptionDefault
limitNoMaximum charts to return. Default 10.
queryNoSearch term, e.g. "pricing", "claude", "inference", "sdk"

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. Changed4 schema fields changed
    • 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\""
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context: the archive grows by one chart per day and the response reports its current size, which tells the agent results are a moving corpus. It does not discuss ordering or pagination beyond the schema's limit.

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?

Front-loaded with the core action in the first clause, then return contents, then archive-size context; three sentences with no filler. The return-field list is slightly redundant with the output schema but remains scannable and useful.

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 two-parameter search tool with an output schema documenting return values and annotations covering safety, nothing an agent needs in order to call it correctly is missing. The growing-archive note and field coverage make the retrieval semantics unambiguous.

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 exceeds it by specifying which fields the query term matches against (title, claim, takeaway, keywords) — information the schema's generic "Search term" text does not convey. The limit parameter is left to the schema, which is reasonable.

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?

States a specific verb ("Searches") and resource ("every chart in the Mode VC Chart of the Day archive") and narrows the scope to keyword matching over title, claim, takeaway and keywords. That framing implicitly separates it from the single-chart getter sibling, since this covers the whole archive rather than one day's entry.

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 "by keyword" — an agent knows to use this when it has a search term rather than a date. However, the description never states when not to use it or names the alternative for fetching today's chart or chart data, leaving the routing decision to inference from sibling names.

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