Skip to main content
Glama

Get a link to watch the diagram

share_link
Read-only

Validates a diagram and returns a Fluxygram link to watch it animated, edit or present it full screen without uploading or storing data.

Instructions

Validates the diagram and returns links on fluxygram.app to watch it animated, open it in the editor or present it full screen. The diagram travels inside the link (compressed); nothing is uploaded or stored. Give the view link to the user.

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": {
      "diagram": "<diagram>"
    },
    "name": "share_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
diagramYesThe diagram: the JSON object or its text.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description adds real value on top: the diagram is compressed inside the link, nothing is uploaded or stored, and the tool validates before returning links. It does not say what happens when validation fails (error vs. partial links), which is the one remaining behavioral gap.

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?

Three short sentences, front-loaded with the primary outcome (links) followed by the privacy note and the action instruction. Every sentence carries information, with no padding or repetition.

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 one-parameter, read-only tool with no output schema, the description covers what is returned (three link types), where the content lives, and what to do with the result. Error behavior on an invalid diagram and link longevity are the only unaddressed details.

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 coverage is 100% and the single parameter already documents that it accepts the diagram as either a JSON object or its text. The description's note that the diagram travels inside the link adds a little meaning about accepted content, but no further syntax or format guidance beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a concrete verb and result: validates the diagram and returns fluxygram.app links for watching, editing, or presenting full screen. It is distinguishable from siblings in that its output is links, but leading with "Validates the diagram" overlaps with the sibling validate_diagram without explicitly separating the two.

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?

"Give the view link to the user" gives a clear delivery instruction for the returned link, which implies when this tool is appropriate (when the user wants to view/present a diagram). It stops short of stating exclusions or naming validate_diagram as the alternative when only validation is wanted.

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

Deploy Server

Other Tools