DoubleData MCP

Get proxy credential

get_credential

Read-only

Retrieve a credential’s gateway hosts and ports for proxy connections, keeping the password masked unless explicitly revealed so agents can use credentials without exposing secrets.

Instructions

Return one credential with gateway hosts and ports. The password is masked unless reveal_password is true; prefer proxy tools, which use the password without showing it.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "username": "<username>"
    },
    "name": "get_credential"
  }
}

Input Schema

Name	Required	Description	Default
`username`	Yes
`reveal_password`	No	Show the plaintext password. Only when the user explicitly needs it.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 9, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is known. The description adds genuinely new behavior: the password is masked by default and only unmasked under an explicit flag, which tells the agent the default response is partially redacted. It does not cover error cases (e.g. unknown username) or whether reveal_password is audited.

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?

Two short sentences with zero waste; the return shape comes first and the security-relevant caveat second. Nothing is buried or repeated.

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?

With no output schema, the description carries the burden of describing the return, and it does so at a high level (credential with gateway hosts and ports). It could enumerate the remaining credential fields or note behavior for missing credentials, but it is sufficient for correct invocation.

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 50%: reveal_password is already documented in the schema, and the description only restates its effect while reinforcing the default-masking behavior. username is undocumented in both places, so the description does not compensate for that gap beyond implying a single lookup key.

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 ("Return one credential") and names the payload contents (gateway hosts and ports), which distinguishes it from the list/export siblings. It never names list_credentials explicitly, so the single-vs-many contrast is only implied.

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?

"Prefer proxy tools, which use the password without showing it" gives a clear routing rule away from this tool for the common case. It does not state when fetching a credential is the right choice, but the preference statement plus the reveal_password caveat covers the main decision.

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