eo-mcp

Overview Schema Source Related Servers Discussions Admin

get_credential_status

Inspect satellite provider credentials, zero-config mode, and active capabilities. Get a JSON summary of masked accounts and unlocked satellite APIs for quick status verification.

Instructions

Inspect the current status of all satellite provider credentials, zero-config mode, and active capabilities.

Returns: JSON string detailing configured accounts (masked for privacy) and unlocked satellite APIs.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 23, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It usefully states that the result is a JSON string, accounts are masked for privacy, and it reports configured accounts plus unlocked APIs. This goes beyond a generic status description, though it could further clarify what 'zero-config mode' means or how failures are reported.

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 two focused sentences, front-loading the main purpose and then clearly noting the return format. Every sentence adds value, and there is no redundant restatement of the tool name.

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 zero-parameter status tool with an output schema, the description is complete: it explains what is inspected, what the result contains, and that sensitive data is masked. No critical operational detail is missing for an agent to invoke this tool correctly.

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, so there is no parameter-semantics burden on the description. The schema coverage is effectively complete, and the description adds relevant context about the output content without needing to explain parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses the specific verb 'Inspect' and clearly identifies the resource: 'current status of all satellite provider credentials, zero-config mode, and active capabilities.' This makes the tool's read-only purpose distinct from siblings like configure_credentials.

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 the tool is for checking credential/configuration status, but it does not explicitly state when to prefer this tool over configure_credentials or other siblings. Context such as 'before configuring credentials' or 'to verify setup' would improve routing, but the purpose is clear enough to infer usage.

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