action1-mcp-server

Resolve endpoint group by name (fuzzy)

action1_endpoint_groups_resolve

Read-onlyIdempotent

Resolve an endpoint group by name or UUID using exact-id, exact-name, starts-with, or contains matching to find the right group for scripts, updates, and endpoint lookups.

Instructions

Look up an endpoint group by name or UUID using exact-id/exact-name/starts-with/contains.

Input Schema

Name	Required	Description
`query`	Yes	Group name fragment or UUID.
`org_id`	No	Org UUID.
`response_format`	No	Output format. Default markdown.

Output Schema

Name	Required	Description
`matches`	No	array
`total_groups`	No	number
`match_strategy`	No	string

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 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 / match_strategy

Added value: +{
+  "description": "string"
+}

addedOutput schema / properties / matches

Added value: +{
+  "description": "array"
+}

addedOutput schema / properties / total_groups

Added value: +{
+  "description": "number"
+}

First observedv0.5.0Jun 27, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, so safety is covered. The description adds useful fuzzy-match semantics (exact-id/exact-name/starts-with/contains), but it does not explain precedence among modes, multiple-match behavior, or error conditions.

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?

A single front-loaded sentence with no redundant or filler content. Every phrase contributes to identifying the operation and its matching behavior.

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?

The tool is simple with full schema coverage, annotations, and an output schema, so return values and safety do not need description space. However, for a fuzzy resolver, the description omits important ambiguity behavior, such as whether multiple matches are returned and whether exact matches take precedence.

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?

Schema coverage is already 100%, so baseline is 3. The description adds meaningful semantics beyond the schema by naming the matching strategies used for the query parameter, which the schema only calls a 'name fragment or UUID.'

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 description states a specific verb (look up/resolve) and resource (endpoint group) and names the query strategies. It is distinguishable from mutation siblings like create/update/delete group, though it does not explicitly contrast with get_group or list_endpoint_groups.

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?

The matching modes imply how to use it for exact or fuzzy lookups, but the description gives no explicit when-to-use guidance versus get_group or list_endpoint_groups. It also does not say when to avoid fuzzy resolution or what to do on ambiguous matches.

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

Deploy Server