Skip to main content
Glama

Autario

by com.autario
OverviewDiscussionsAdmin

list_charts

Read-onlyIdempotent

List published chart visualizations on Autario, built on the public catalog (World Bank, FRED, Eurostat, OECD, WHO, IMF, SEC) and rendered with Plotly. Returns chart IDs, titles, insights, linked datasets, and creation dates. Use to discover existing analyses before building a new one, and to find a shareable autario.com/chart/{id} link for an answer.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoSearch term to filter charts by title or question
limitNoMaximum number of charts to return (default 20, max 100)
formatNoOutput wire format for this MCP call. Default 'toon' (Token-Oriented Notation, fewest tokens, best for tabular rows). 'compact' = minified JSON. 'json' = pretty JSON for readability. The REST API always returns JSON regardless.
offsetNoNumber of charts to skip for pagination

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / format / description
      Previous value: -"Output wire format. 'compact' (default) = minified JSON, token-efficient. 'json' = pretty JSON for readability. 'toon' = Token-Oriented Notation, fewest tokens for tabular rows."New value: +"Output wire format for this MCP call. Default 'toon' (Token-Oriented Notation, fewest tokens, best for tabular rows). 'compact' = minified JSON. 'json' = pretty JSON for readability. The REST API always returns JSON regardless."
    • changedInput schema / properties / format / enum
      Previous value: -[
-  "compact",
-  "json",
-  "toon"
-]New value: +[
+  "toon",
+  "compact",
+  "json"
+]
  2. Changed1 schema field changed
    • addedInput schema / properties / format
      Added value: +{
+  "description": "Output wire format. 'compact' (default) = minified JSON, token-efficient. 'json' = pretty JSON for readability. 'toon' = Token-Oriented Notation, fewest tokens for tabular rows.",
+  "enum": [
+    "compact",
+    "json",
+    "toon"
+  ],
+  "type": "string"
+}
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover readOnlyHint, idempotentHint, destructiveHint, so the bar is lower. The description adds useful behavioral context beyond annotations by specifying data sources (World Bank, FRED, etc.), rendering library (Plotly), and the exact return contents (chart IDs, titles, insights, linked datasets, creation dates).

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?

The description is compact and front-loaded with the core action, then adds relevant source context and usage guidance. Every sentence contributes value; the data-source list is slightly verbose but helps set expectations about chart coverage.

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?

With no output schema, the description still explains what is returned and how to use the results. It covers the tool's purpose, scope, return fields, and typical use cases, making it complete for a read-only listing tool.

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?

The input schema already has 100% description coverage for all four parameters, including q, limit, format, and offset. The description does not add new parameter-level meaning, so the baseline score of 3 is appropriate.

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?

The description begins with a specific verb and resource—'List published chart visualizations on Autario'—and clearly separates this from siblings like get_chart (singular retrieval) and list_chart_candidates (candidate charts). It also enumerates the returned fields, making the tool's purpose immediately identifiable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says to use this tool 'to discover existing analyses before building a new one' and to 'find a shareable autario.com/chart/{id} link for an answer.' This provides clear usage context, though it does not explicitly name alternative tools or state when not to use it.

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

All Autario 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