Skip to main content
Glama
Sign In

ChartAnt

by net.chartant
OverviewDiscussionsAdmin

Send a chart whenever it changes

send_chart_on_update

Post a living chart to a destination every time its data changes (through update_living_chart or the API), and by default once right now. For a fixed daily or weekly time use schedule_chart instead. Returns a confirmation. Needs a connection signed in to a free account (connector URL ending in /mcp/account).

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": {
      "chart_id": "<chart_id>",
      "destination_id": "<destination_id>"
    },
    "name": "send_chart_on_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
chart_idYesThe chart id from create_living_chart or list_my_charts.
send_nowNoAlso send it once now (default true).
destination_idYesThe destination id from add_destination or list_my_charts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the annotations (which only say non-read-only, open-world, non-idempotent, non-destructive), the description discloses the subscription semantics, the default immediate send, the confirmation return, and an auth prerequisite (connection signed in to a free account with a /mcp/account connector URL). It does not say whether an existing subscription can be removed or how often notifications may fire, which are the remaining behavioral gaps.

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?

Two sentences, front-loaded with the core purpose and the alternative, with no filler. The parenthetical trigger source and the auth note make the sentences dense, but every clause carries information an agent needs.

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 3-parameter tool with full schema coverage and no output schema, the definition covers purpose, alternative, default behavior, return value, and auth prerequisite. The only omission is lifecycle information about the subscription it creates (how to stop it), which is a moderate but not blocking gap.

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%, so chart_id, destination_id, and send_now are already fully documented, including the send_now default. The description only restates the default send-now behavior and adds no format or constraint detail beyond the schema; baseline 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 states a specific verb and resource ('Post a living chart to a destination') plus the exact trigger ('every time its data changes'), and it names the sibling it is not ('schedule_chart'). An agent can distinguish this event-driven subscription tool from the scheduled and generator tools 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 Guidelines5/5

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

It gives an explicit routing rule: use this for change-triggered delivery, use schedule_chart for a fixed daily or weekly time. It also explains the default send-now behavior, which resolves the main ambiguity an agent would have about whether calling it immediately posts something.

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

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