DataSnack

Export a model to Excel

export_model

Idempotent

Create an Excel workbook of a DataSnack model the signed-in reader covers, with the model's equations as working formulas, its inputs and its record, and return a download link. Waits up to 20 seconds for the workbook; get_export finishes a slower one.

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": {
      "id": "<id>"
    },
    "name": "export_model"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	A DataSnack model id (ch:…) or a datasnack.ai/m/… URL

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.3/5.0

Behavior4/5

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

The annotations declare readOnlyHint=false and idempotentHint=true, so the agent knows this materializes something server-side but is safe to repeat. The description adds genuinely non-redundant behavior: a 20-second bounded wait, a download-link return, and the precise workbook contents. It stops short of saying whether the artifact persists or how long the link lives.

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?

Two sentences, both earning their place: the first covers what is produced and returned, the second covers the timeout and the fallback tool. Content description is front-loaded ahead of the escape hatch, so the most important information lands first.

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 one-parameter export tool with no output schema, the description supplies the return shape (download link), the timeout behavior, the failure fallback, and the workbook payload. Nothing an agent needs in order to call it and interpret the result is missing.

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 'id' parameter already documents both the 'ch:…' id form and the datasnack.ai/m/… URL form. The description only adds the access constraint that the reader must cover the model, not any new syntax or format detail. Baseline 3 is appropriate when the schema carries the parameter burden.

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 ('Create an Excel workbook of a DataSnack model') and enumerates what goes into it (equations as working formulas, inputs, record). It also distinguishes itself from get_export by scope: this one returns a download link after a bounded wait, while get_export handles slower runs.

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?

Explicitly routes the agent to the alternative: 'Waits up to 20 seconds for the workbook; get_export finishes a slower one,' which tells the caller what to do on timeout. It also embeds a prerequisite ('a model the signed-in reader covers') that constrains when the call will succeed. No explicit when-not guidance beyond the timeout path, so not a full 5.

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

All DataSnack tools Inspect

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

Need Help?