Skip to main content
Glama
Sign In
mguttmann

action1-mcp-server

by mguttmann
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get Deployer installation URL

action1_get_windows_deployer_url
Read-onlyIdempotent

Retrieve the Deployer installation URL for an organization so you can download the Deployer setup file. Provide the org UUID to get the download link.

Instructions

Get Deployer installation URL. Obtains an URL to download the Deployer installation file. Perm: manage_endpoints.

Input Schema

NameRequiredDescriptionDefault
org_idNoOrg UUID.
verboseNoSkip per-item compactor.
response_formatNoOutput format. Default markdown.

Output Schema

NameRequiredDescriptionDefault
idNo
selfNo
typeNo
download_URLNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.6.0
    • 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 / download_URL
      Added value: +{}
    • addedOutput schema / properties / id
      Added value: +{}
    • addedOutput schema / properties / self
      Added value: +{}
    • addedOutput schema / properties / type
      Added value: +{}
  2. First observedv0.5.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds the useful auth requirement 'Perm: manage_endpoints', but says nothing about whether the URL expires, is org-scoped, or is single-use.

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?

Two sentences plus a permission note, front-loaded with the action. The second sentence largely restates the first ('Get... URL' vs 'Obtains a URL to download...'), a small redundancy but no real bloat.

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?

An output schema exists, so return values need not be explained, and the permission note covers auth. But with zero required parameters, an agent is left unsure whether org_id is effectively mandatory and how this differs from the agent-install-URL sibling.

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%, so org_id, verbose and response_format are already documented. The description adds no extra meaning about which org the URL is issued for or how verbose/response_format affect the returned link, so 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?

States a specific verb and resource ('Get Deployer installation URL' / 'Obtains an URL to download the Deployer installation file'). It does not, however, distinguish this from the very similar sibling action1_get_agent_install_url, which an agent could easily confuse it with.

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 statement of when to choose this over action1_get_agent_install_url, action1_list_endpoint_deployers, or action1_get_deployer. The only contextual hint is the permission prerequisite, which describes access rather than selection.

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