Nest Protect MCP Server

get_mcp_config

Retrieve active server configuration for API endpoints, timeouts, and device filters.

Instructions

Get Current Server Configuration.

Retrieve the active configuration values for API endpoints, timeouts, and device filters.

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": {
      "params": "<params>"
    },
    "name": "get_mcp_config"
  }
}

Input Schema

Name	Required	Description	Default
`params`	Yes	Parameters for getting config section.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 10, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations provided. Description indicates read-only behavior ('retrieve'), but does not explicitly state safety or side effects. Basic transparency exists but lacks depth.

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 concise sentences with no unnecessary text. Front-loaded with the main action: 'Get Current Server Configuration.'

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?

Adequate for a simple read operation with one parameter and no output schema. Describes what config contains, but could mention structure of return value for completeness.

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?

Input schema has full description coverage (100%). Description adds value by listing examples of config contents ('API endpoints, timeouts, device filters') that are not in schema descriptions.

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?

Description clearly states 'Get Current Server Configuration' with specific verb 'retrieve' and resource 'active configuration values for API endpoints, timeouts, and device filters'. Distinguishes from sibling write/update tools like update_mcp_config and reset_mcp_config.

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?

No explicit guidance on when to use this tool versus alternatives (e.g., update_mcp_config for modifications). Usage is implied by the read nature, but not stated.

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