Skip to main content
Glama

Find a chart or dataset

search_charts
Read-onlyIdempotent

Search the site's charts by topic or question (e.g. "bear markets", "Shiller CAPE", "Nasdaq 100 drawdown", "monthly seasonality"). Returns each chart's title, the question it answers, its page and the dataset path to pass to get_dataset.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_charts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoDefault 10.
queryYesWords to match against chart titles and the questions they answer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds value beyond them by disclosing the return payload (title, question, page, dataset path) despite there being no output schema, which is the key behavioral trait an agent needs for chaining.

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 sentences, zero filler. The core purpose and query-matching scope come first, and the return-shape/chaining detail follows immediately. Nothing is repeated from the schema or annotations.

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

Completeness4/5

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

For a simple two-parameter closed-world search with no output schema, the description covers both what goes in (topic/question queries) and what comes back (title, question, page, dataset path) plus the handoff to get_dataset. The only gap is routing guidance relative to the other lookup siblings.

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 description coverage is 100%, so the baseline is 3. The description goes slightly beyond the schema by giving example query strings ('bear markets', 'Shiller CAPE', 'Nasdaq 100 drawdown', 'monthly seasonality'), which concretely illustrates what shapes of query will match, though it says nothing about the limit parameter.

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 and resource ('Search the site's charts') and scopes it to topic or question matching, with concrete example queries. It also names the downstream sibling get_dataset and the exact field (dataset path) that chains into it, so an agent can distinguish this discovery tool from the retrieval siblings without opening any schema.

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 rather than stated: the mention that results include 'the dataset path to pass to get_dataset' signals this is a first-step discovery tool in front of get_dataset. However, there is no explicit when-to-use/when-not guidance and no comparison against annual_returns, get_latest, or index_changes, so the agent must infer the routing.

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