Skip to main content
Glama

chartlink

by io.github.oscarleoo
OverviewDiscussionsAdmin

Templates by need — search, then start a chart from the best match

list_templates
Read-onlyIdempotent

Templates are named by the NEED they answer (need, asks, tags), each with urls.png (show it to your human) and columns: the column ids your data must supply. Pass q with what the person asked for — "map of brazil's states", "ranked bars with flags", "change between two years" — and the list comes back ranked; take the first. Then create_asset with template: and your data — the whole design comes along. Any chart id you were shown works as a template too, not only these.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoWhat is needed, in the person's words
tagsNoComma-separated tags every result must carry, e.g. map,united-states
typeNoOnly this asset type, e.g. "bar"
limitNoAt most this many, best first (default 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "At most this many, best first (default 20)",
+  "maximum": 200,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / tags
      Added value: +{
+  "description": "Comma-separated tags every result must carry, e.g. map,united-states",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / q
      Added value: +{
+  "description": "What is needed, in the person's words",
+  "type": "string"
+}
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already provide read-only and idempotent safety, and the description adds genuinely useful behavior: results are ranked, each result carries urls.png and required columns, and template ids are usable downstream. It does not discuss matching mechanics or empty-result behavior, but that is minor for a safe search operation.

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?

Four sentences carry a lot of signal without padding: template naming, result contents, how to pass q, and the downstream create_asset step. Key usage instructions are front-loaded and every sentence earns its place.

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?

Even without an output schema, the description conveys the return shape enough for an agent: a ranked list of templates with urls.png, columns, and template ids. It omits minor edge cases such as empty search results, but the workflow and data contract are sufficiently clear for this read-only search tool.

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?

The schema already documents all four parameters with 100% coverage, so the baseline is 3. The description adds value beyond the schema by explaining q with natural-language examples and clarifying that results are ordered best-first, which reinforces the purpose of 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?

The description and title clearly identify list_templates as a search/discovery tool: templates are keyed by the need they answer, and passing q returns a ranked list with the instruction to take the first. This distinguishes it from get_template or create_from_template by framing it as the discovery step before asset creation.

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?

It gives an explicit workflow: form q from the person's words, take the top ranked hit, then hand the template id to create_asset; it also notes that any already-known chart id can be used as a template, implying when listing is unnecessary. It does not explicitly name alternative sibling tools like get_template or state when not to use this tool.

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

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