Systems Manager

Systems Ingest Host

systems_ingest_host

Ingests keyed host telemetry as typed HardwareNode, NetworkInterface, and DiskVolume nodes through a governed ChangeEnvelope boundary for controlled host data onboarding.

Instructions

Ingest a keyed host telemetry projection through the governed ChangeEnvelope boundary as typed HardwareNode, NetworkInterface, and DiskVolume nodes.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.2.5Oct 24, 2026

TDQS

C2.7/5.0

Behavior2/5

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

With no annotations, the description carries the full behavioral burden. 'Ingest' implies a write/mutation and 'governed ... boundary' hints at a policy gate, but nothing is said about side effects, idempotency, permissions, failure modes, or what a successful ingest produces. The jargon gestures at governance without disclosing any concrete behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single front-loaded sentence with no wasted preamble, which is good. But the sentence is packed with unexpanded domain coinages ('keyed', 'ChangeEnvelope boundary', 'typed ... nodes') whose density substitutes for clarity rather than conveying it.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema and no annotations mean the description must explain the input source, the response, and side effects, and it does none of these. For a zero-parameter mutation-style tool operating on host hardware/network/disk telemetry, an agent still cannot tell what triggers it or what it returns.

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?

There are zero parameters and 100% schema coverage, so per the baseline nothing needs to be explained at the parameter level. The description does, however, leave unaddressed how a zero-argument tool obtains telemetry, which is a gap better attributed to contextual completeness.

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

Purpose3/5

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

The verb 'Ingest' and the object 'host telemetry projection' identify a rough action, and the description names the resulting node types (HardwareNode, NetworkInterface, DiskVolume). However, 'keyed host telemetry projection' and 'governed ChangeEnvelope boundary' are internal jargon that does not tell an agent what data goes in or where it comes from, and nothing distinguishes this from the many sibling system tools.

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 use this tool, when not to, or which of the roughly 25 siblings (capture_system_snapshot, sm_disk_operations, get_network_connections) it replaces or complements. The agent must infer usage from the name alone.

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