Skip to main content
Glama

BaseEdge Labs Catalog

Get a preset

get_preset
Read-onlyIdempotent

One preset in full, to explain it: what it is for, its results, the Strategy Tester properties to set (commission, slippage, capital), and every input value by its label.

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": "get_preset"
  }
}

Input Schema

NameRequiredDescriptionDefault
preset_idYesA preset_id from list_presets

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, idempotentHint, non-destructive and closed-world, so safety is covered; the description adds genuine value by disclosing the return payload: purpose, results, Strategy Tester properties (commission, slippage, capital) and every input value by label. That is meaningful behavioral context an agent cannot get from the annotations, with no 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?

One compact sentence with the outcome ("one preset in full") front-loaded and no filler. The colon-list is dense but readable; "to explain it" is the only slightly loose phrase.

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?

With no output schema, the description usefully enumerates what the response contains, which is the main thing an agent needs to know before deciding to call it. Only the discovery path for preset_id is left to the schema, which covers it adequately.

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?

There is a single parameter with 100% schema description coverage that already says it is a preset_id from list_presets. The description adds no format, sourcing, or error behavior beyond that, so the baseline 3 applies.

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?

"One preset in full" plus the enumerated contents makes clear this is a single-record fetch of a preset by id, implicitly contrasted with the listing sibling. The retrieval verb is only implied ("One preset in full") rather than stated, but an agent can still tell this apart from list_presets and export_preset.

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?

"to explain it" hints at the use case (explaining a preset to a user) and the schema ties preset_id back to list_presets, but the description itself gives no explicit when-to-use or when-not guidance and never names a sibling tool. Usage has to be inferred from context.

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