action1-mcp-server

Get a setting template

action1_get_setting_template

Read-onlyIdempotent

Retrieve details of a specific setting template by its ID. Use this to inspect configuration templates for endpoint management.

Instructions

Get a setting template. Gets details about a setting template specified by its ID.

Input Schema

Name	Required	Description
`verbose`	No	Skip per-item compactor.
`template_id`	Yes	Provide a specific setting template ID.
`response_format`	No	Output format. Default markdown.

Output Schema

Name	Required	Description	Default
`id`	No
`name`	No
`self`	No
`type`	No
`category`	No
`value_type`	No
`description`	No
`default_value`	No
`value_pattern`	No
`applicable_for`	No
`available_scopes`	No
`value_pattern_description`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed15 schema fields changedv0.6.0Oct 26, 2026
- changedInput schema / $schema
```
Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
```
- changedOutput schema / $schema
```
Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
```
- changedOutput schema / additionalProperties
```
Previous value: -trueNew value: +{}
```
- addedOutput schema / properties / applicable_for
```
Added value: +{}
```
- addedOutput schema / properties / available_scopes
```
Added value: +{}
```
- addedOutput schema / properties / category
```
Added value: +{}
```
- addedOutput schema / properties / default_value
```
Added value: +{}
```
- addedOutput schema / properties / description
```
Added value: +{}
```
- addedOutput schema / properties / id
```
Added value: +{}
```
- addedOutput schema / properties / name
```
Added value: +{}
```
- addedOutput schema / properties / self
```
Added value: +{}
```
- addedOutput schema / properties / type
```
Added value: +{}
```
- addedOutput schema / properties / value_pattern
```
Added value: +{}
```
- addedOutput schema / properties / value_pattern_description
```
Added value: +{}
```
- addedOutput schema / properties / value_type
```
Added value: +{}
```
First observedv0.5.0Jun 27, 2026

TDQS

C2.7/5.0

Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered externally. The description adds nothing beyond that — no note on error behavior for an unknown ID, no hint about what the template object contains, and no mention that IDs must come from the list tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, but the second is a near-verbatim restatement of the first and earns no place. There is no waste in length, but also no information gain — the space could have carried sibling differentiation instead.

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?

Given an output schema exists (return shape need not be explained), 100% schema coverage, and full annotation coverage, the essentials for invoking the tool correctly are all present in the structured fields. The remaining gap is conceptual — template vs. setting vs. template list — which is a usage issue rather than a completeness blocker.

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% for all three parameters, so baseline is 3. The description only echoes template_id ('specified by its ID') and says nothing about verbose or response_format, leaving the schema to do all the work.

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

Purpose3/5

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

The description names a clear verb+resource (get a setting template) and adds that it is 'specified by its ID,' but the second sentence only restates the first. Nothing distinguishes it from siblings such as action1_list_setting_templates, action1_get_setting, or action1_get_action_template, so an agent gets adequate but not discriminating purpose information.

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?

There is no guidance on when to call this versus action1_list_setting_templates (to discover IDs) or action1_get_setting (for instantiated settings rather than templates). The agent must infer the distinction from tool names alone.

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

Deploy Server