Skip to main content
Glama
Sign In
controld-mcp

controld-mcp

by SwaggyMike
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List redirect locations

list_proxy_locations
Read-onlyIdempotent

List available Control D proxy locations and their IDs to configure redirect rules.

Instructions

List Control D proxy locations and IDs for redirect rules.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is clear. The description adds that it lists locations and IDs, but does not disclose additional behavioral traits like pagination or output format. With annotations covering safety, a 3 is appropriate.

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?

The description is a single sentence with no wasted words. It is front-loaded with the verb 'List' and clearly states the resource and purpose. Perfectly concise.

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 the tool has no parameters, no output schema, and simple purpose, the description is complete enough. It explains what the tool returns (locations and IDs) and their use case (redirect rules). The sibling tools are mostly about rules and profiles, so this tool's role is clear.

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 has zero parameters, and schema coverage is 100% (empty schema). The description adds meaning by specifying what is listed (proxy locations and IDs) and their purpose (for redirect rules), which is useful context beyond the empty schema. Baseline 4 for zero params is justified.

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 clearly states the tool lists Control D proxy locations and IDs for redirect rules, which is a specific verb+resource. It distinguishes from siblings like list_profiles and list_endpoints by focusing on proxy locations for redirect rules, though it could be more explicit about the distinction.

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 description implies usage for redirect rules but does not explicitly state when to use this tool versus alternatives. It lacks guidance on when not to use it or mention of alternatives, but the context of redirect rules provides some clarity.

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