Skip to main content
Glama
Sign In

ChartAnt

by net.chartant
OverviewDiscussionsAdmin

Add a place to send charts

add_destination

Save a destination that charts can be sent to: 'slack', 'teams' or 'discord' (needs the channel's incoming webhook URL, which the user creates in that app), 'email' (the user's own confirmed address, no URL), or 'webhook' (any https URL; requests are signed). Nothing is sent yet; connect a chart to it with send_chart_on_update or schedule_chart. Returns the destination id. 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": {
      "type": "<type>",
      "name": "<name>"
    },
    "name": "add_destination"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoThe incoming webhook URL (not for email).
nameYese.g. '#metrics' or 'My inbox'
typeYesWhere to send: slack, teams, discord, email or webhook.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare non-read-only, non-destructive, non-idempotent behavior; the description adds real value beyond them by explaining the per-type prerequisites (user-created incoming webhook, confirmed email address, any https URL with signed requests) and by stating that the call returns the destination id and sends nothing yet. The only small gap is that the requirement text about the free account is dense and the openWorldHint=false annotation sits in mild tension with arbitrary https webhook URLs, though it is not a true contradiction.

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 and value list, and every clause carries operational information; the heavy parenthetical nesting in the first sentence slightly hurts scannability but no sentence is wasted.

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 3-parameter creation tool with no output schema, the description covers prerequisites, per-type requirements, side effects (nothing sent yet), follow-up tools, and return value, leaving nothing an agent needs to call it correctly.

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 baseline is 3, and the description goes further by explaining the semantics of url per type (webhook URL the user creates in the app, no URL for email) and giving a concrete example shape for name ('#metrics', 'My inbox').

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?

Names a specific verb and resource ('Save a destination that charts can be sent to') and enumerates exactly the five supported destination types, so the agent immediately knows the scope without opening the 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?

Explicitly states 'Nothing is sent yet' and routes the agent to send_chart_on_update or schedule_chart for the actual delivery step, and states the authentication prerequisite (connection signed in to a free account, connector URL ending in /mcp/account). Nothing about when/when-not is left to inference.

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