Skip to main content
Glama

List Editable Strategy Fields

tt_list_editable_fields
Read-onlyIdempotent

List the top-level fields that tt_update_strategy can change.

Returns the canonical list with type, description, and example value for each. Use this when the user asks "what can I change?" or to confirm a field is editable before composing an edit.

Structural changes (adding/removing/reordering sets, conditions, or legs) are NOT in this list, but both structural doors exist: tt_apply_strategy_patch (JSON-Patch, preferred — per-op diff + dry_run) and tt_update_strategy with a full replacement sets array. You do not need to recreate the strategy for a structural edit.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tt_list_editable_fields"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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 readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds value beyond that: it discloses the return payload (canonical list with type, description, and example value per field) and the negative scope (structural changes are absent), which prevents an agent from assuming the list is exhaustive. It does not mention pagination or size, but for a fixed canonical field list that is minor.

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 one-sentence definition, followed by return shape, then usage trigger, then scope caveat. Every sentence is relevant, though the final reassurance ("You do not need to recreate the strategy for a structural edit") is slightly editorial and could be folded into the alternative-routing sentence.

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?

With no output schema, the description carries the burden of describing the response and does so (type, description, example value per field). Combined with the explicit scope boundary and sibling routing, an agent has everything needed to call this tool correctly at the right moment.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline is 4. The description correctly implies a no-argument call rather than suggesting any filtering options.

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?

States a specific verb+resource ("List the top-level fields that tt_update_strategy can change") and immediately bounds the scope by declaring what is excluded (structural changes to sets/conditions/legs). An agent can distinguish this read-only introspection tool from tt_update_strategy and tt_apply_strategy_patch without opening any 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?

Gives an explicit trigger ("when the user asks 'what can I change?'" or to confirm a field is editable before composing an edit) and explicitly routes structural edits to tt_apply_strategy_patch (marked preferred) or a full replacement via tt_update_strategy. Both the when and the when-not are stated with named alternatives.

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