Skip to main content
Glama

BaseEdge Labs Catalog

Export a preset

export_preset
Read-onlyIdempotent

Download links for a preset's files. "hypernull": the HyperNull extension's preset file (name, strategy, instrument and timeframe included). "tradingview": a flat, label-keyed settings file for TradingView's Load Parameters.

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": {
      "preset_id": "<preset_id>"
    },
    "name": "export_preset"
  }
}

Input Schema

NameRequiredDescriptionDefault
preset_idYesA preset_id from list_presets

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare read-only, idempotent, non-destructive, and closed-world behavior. The description adds useful detail about the two output file formats, but does not mention link expiration, permission requirements, or the response envelope.

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?

The description is compact and front-loaded, with the two format keys defined efficiently. It is slightly less polished because the first sentence is a fragment and the quoted labels are abrupt.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Because there is no output schema, the description must explain return values; it does so at a high level by naming the two file outputs but does not specify the exact response structure or link lifecycle. For a one-parameter read-only export tool, this is adequate but incomplete.

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%, and the only parameter, preset_id, is documented as coming from list_presets. The description adds no additional meaning about how preset_id is used.

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?

The opening sentence, 'Download links for a preset's files,' identifies the exported resource and the two file formats, so an agent can tell this exports files rather than retrieving preset metadata. It does not explicitly contrast with siblings such as get_preset or list_presets.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The description does not state when to use this tool versus get_preset, list_presets, or other alternatives. Usage is only implied by the mention of download links and file formats.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources