Skip to main content
Glama
DanFashauer

SignalGrid MCP

by DanFashauer

signalgrid_posture_report

Read-onlyIdempotent

Get a full device trust snapshot in a single round-trip: identity, OS, security, MDM, patch state, and optional sections. Reduces six calls to one and can include a fail-safe verdict.

Instructions

Full device trust snapshot in a single round-trip: identity + OS + security + MDM + patch state by default, with optional extra sections.

Use this first. One call instead of six, which matters when every tool call is a network round-trip. Drill into the focused tools afterward for anything that looks off. A failed section reports {"error": ...} instead of sinking the whole snapshot.

Set include_verdict=True to also get the on-device SignalGrid decision as a 'verdict' summary alongside the raw facts — the same fail-safe fold as signalgrid_trust_verdict (unknown is never 'allow'). The verdict is a derived summary, never a collected signal, so it is absent unless explicitly asked for.

Args: sections: optional list from {identity, os, security, sharing, mdm, updates, xprotect, network, persistence, time_machine, system_extensions, screen_lock}. include_verdict: attach the folded allow/step_up/restrict/deny verdict.

Returns: dict keyed by section name; each value is that section's collector output (same shapes as the corresponding focused tools). With include_verdict, an extra 'verdict' key holds the folded decision.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sectionsNoWhich sections to include. Default: identity, os, security, mdm, updates, xprotect. Also available: sharing, network, persistence, time_machine, system_extensions, screen_lock. Pass an explicit list to customize.
include_verdictNoAlso fold the posture into the fail-safe SignalGrid verdict (allow / step_up / restrict / deny) under a 'verdict' key. Default False (the report stays purely factual). When True, the sections the verdict needs (security, mdm, updates, xprotect, system_extensions) are collected even if not in `sections`.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive. The description adds valuable behavioral context: failed sections return an error dict without sinking the whole snapshot, the verdict is a derived summary (absent unless requested), and include_verdict auto-collects required sections. No contradiction with annotations.

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

Conciseness4/5

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

The description is well-structured with a strong opening summary, usage guidance, and an Args/Returns section. It is a bit longer than strictly necessary, but every part serves a purpose—no filler or repetition of annotations.

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?

Given the moderate complexity (two optional params, many section choices), the description fully explains return shapes, error behavior, and verdict derivation. Combined with rich schema and annotations, the agent has all needed context to invoke the 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?

Schema already covers both parameters at 100%. The description adds meaning by explaining the fail-safe verdict semantics and the 'unknown is never allow' policy, which is beyond the schema's field descriptions. Slightly redundant Args block but still adds context.

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 clearly states what the tool does: it returns a full device trust snapshot combining identity, OS, security, MDM, and patch state in one call. It distinguishes itself from siblings by positioning as the 'use this first' aggregate tool, with focused tools as follow-ups.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly advises 'Use this first' and explains the advantage of a single call versus six. It also directs users to drill into focused tools afterward and describes when to set include_verdict, giving clear contextual guidance for tool selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/DanFashauer/signalgrid-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server