Skip to main content
Glama
Sign In
mulewatch

mulewatch

by brbousnguar
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List environments

anypoint_list_environments

List Anypoint Platform environments within a business group to discover available deployment targets; if empty, query business groups for the correct orgId.

Instructions

List the Anypoint environments in a business group. If this returns nothing, the orgId is probably the root organization — call anypoint_list_business_groups to find the right id. Restricted to ANYPOINT_ALLOWED_ENVIRONMENTS when that is set.

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

Input Schema

NameRequiredDescriptionDefault
orgIdNoBusiness group id. Defaults to ANYPOINT_ORG_ID, or the credentials' own organization.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.1/5.0
Behavior4/5

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

No annotations are present, so the description carries the full disclosure burden, and it does add real behavior: output may be filtered by the ANYPOINT_ALLOWED_ENVIRONMENTS setting, and an empty result has a specific diagnostic meaning (root org) rather than 'no data'. It still omits pagination and permission/auth requirements, so it is not exhaustive.

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?

Three tight sentences, front-loaded with the core action, followed by the empty-result remedy and the filtering caveat. No filler and nothing redundant.

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?

For a single optional-parameter list tool with no output schema, the description covers the action, the result caveat, the fallback path, and the filtering constraint. An agent has everything needed to call it correctly and interpret an empty response.

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 coverage is 100%, and the schema already documents the orgId default chain (ANYPOINT_ORG_ID, then credentials' organization). The description only echoes the 'business group' framing and adds the root-org troubleshooting hint, so it does not meaningfully extend parameter meaning beyond the schema.

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?

States a specific verb and resource with scope: 'List the Anypoint environments in a business group.' That is concrete enough for an agent to act on immediately. It does not explicitly contrast itself with the sibling listing tools, though it does route to anypoint_list_business_groups for a specific failure mode.

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

Usage Guidelines4/5

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

Gives an explicit conditional path: if the call returns nothing, the orgId is likely the root organization and the agent should call anypoint_list_business_groups instead. It also flags that results are restricted when ANYPOINT_ALLOWED_ENVIRONMENTS is set, which tells the agent when a partial list is expected rather than a bug.

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

Deploy Server

Other Tools