@shieldlabs-ai/mcp

Official

by ShieldLabs-ai

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

Explain Risk Score

shieldlabs_explain_risk_score

Read-onlyIdempotent

Explains why an identification received its risk score by analyzing pasted ID data or domain UUIDs, clarifying unavailable signal weights and separating HRE confidence from the Risk Score.

Instructions

Read an identification card or explain a pasted identification. Missing signal weights are unavailable, never zero contribution. HRE confidence is separate from Risk Score.

Input Schema

Name	Required	Description	Default
`domain`	No	Public domain UUID from shieldlabs_list_domains, not the hostname.
`identification`	No
`response_format`	No		markdown
`identification_id`	No

Output Schema

Name	Required	Description	Default
`risk`	No
`signals`	Yes
`risk_score`	No
`identification_id`	Yes
`weights_available`	No
`untrusted_data_note`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed25 schema fields changedv1.1.0Oct 31, 2026

addedInput schema / properties / domain

Added value: +{
+  "description": "Public domain UUID from shieldlabs_list_domains, not the hostname.",
+  "pattern": "^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$",
+  "type": "string"
+}

changedInput schema / properties / identification / anyOf

Previous value: -[
-  {
-    "additionalProperties": true,
-    "propertyNames": {
-      "type": "string"
-    },
-    "type": "object"
-  },
-  {
-    "maxLength": 500000,
-    "type": "string"
-  }
-]New value: +[
+  {
+    "additionalProperties": {},
+    "propertyNames": {
+      "type": "string"
+    },
+    "type": "object"
+  },
+  {
+    "maxLength": 500000,
+    "type": "string"
+  }
+]

removedInput schema / properties / identification / description

Removed value: -"An identification to explain without an API call: a normalized identification (for example the json output of shieldlabs_get_identification), a webhook event or its data object, or a raw History API row. A JSON object or its JSON text."

addedInput schema / properties / identification_id

Added value: +{
+  "pattern": "^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$",
+  "type": "string"
+}

removedInput schema / properties / request_id

Removed value: -{
-  "description": "Request ID of the identification to explain, read from the History API (needs SHIELDLABS_API_KEY; waits up to about 10 seconds for a new identification, like shieldlabs_get_identification). Give either request_id or identification.",
-  "pattern": "^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$",
-  "type": "string"
-}

removedInput schema / properties / response_format / description

Removed value: -"Output format: 'markdown' (default) for readable text, 'json' for structured data"

changedOutput schema / additionalProperties
```
Previous value: -falseNew value: +{}
```
removedOutput schema / properties / band_meaning
```
Removed value: -{
-  "type": "string"
-}
```
removedOutput schema / properties / band_range
```
Removed value: -{
-  "type": "string"
-}
```

removedOutput schema / properties / connection_type

Removed value: -{
-  "anyOf": [
-    {
-      "additionalProperties": false,
-      "properties": {
-        "label": {
-          "type": "string"
-        },
-        "meaning": {
-          "type": "string"
-        },
-        "value": {
-          "type": "string"
-        }
-      },
-      "required": [
-        "value",
-        "label",
-        "meaning"
-      ],
-      "type": "object"
-    },
-    {
-      "type": "null"
-    }
-  ]
-}

removedOutput schema / properties / detection_flags

Removed value: -{
-  "items": {
-    "additionalProperties": false,
-    "properties": {
-      "flag": {
-        "type": "string"
-      },
-      "label": {
-        "type": "string"
-      },
-      "meaning": {
-        "type": "string"
-      },
-      "scored": {
-        "type": "boolean"
-      }
-    },
-    "required": [
-      "flag",
-      "label",
-      "scored",
-      "meaning"
-    ],
-    "type": "object"
-  },
-  "type": "array"
-}

addedOutput schema / properties / identification_id

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

removedOutput schema / properties / notes

Removed value: -{
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}

removedOutput schema / properties / request_id

Removed value: -{
-  "anyOf": [
-    {
-      "description": "Request ID of the explained identification, when known",
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ]
-}

addedOutput schema / properties / risk

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "as_of": {
+          "type": "string"
+        },
+        "band": {
+          "enum": [
+            "trusted",
+            "suspicious",
+            "dangerous"
+          ],
+          "type": "string"
+        },
+        "score": {
+          "maximum": 100,
+          "minimum": 0,
+          "type": "integer"
+        },
+        "state": {
+          "const": "ok",
+          "type": "string"
+        }
+      },
+      "required": [
+        "state",
+        "band",
+        "as_of"
+      ],
+      "type": "object"
+    },
+    {
+      "additionalProperties": false,
+      "properties": {
+        "as_of": {
+          "type": "null"
+        },
+        "band": {
+          "type": "null"
+        },
+        "state": {
+          "const": "unavailable",
+          "type": "string"
+        }
+      },
+      "required": [
+        "state",
+        "band",
+        "as_of"
+      ],
+      "type": "object"
+    }
+  ]
+}

removedOutput schema / properties / risk_band

Removed value: -{
-  "enum": [
-    "trusted",
-    "suspicious",
-    "dangerous",
-    "rate_limited"
-  ],
-  "type": "string"
-}

addedOutput schema / properties / signals / anyOf

Added value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "items": {
+        "items": {
+          "type": "string"
+        },
+        "maxItems": 100,
+        "type": "array"
+      },
+      "state": {
+        "enum": [
+          "ok",
+          "unavailable"
+        ],
+        "type": "string"
+      }
+    },
+    "required": [
+      "state",
+      "items"
+    ],
+    "type": "object"
+  },
+  {
+    "items": {
+      "additionalProperties": {},
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "type": "array"
+  }
+]

removedOutput schema / properties / signals / items

Removed value: -{
-  "additionalProperties": false,
-  "properties": {
-    "in_catalog": {
-      "type": "boolean"
-    },
-    "label": {
-      "type": "string"
-    },
-    "meaning": {
-      "type": "string"
-    },
-    "name": {
-      "type": "string"
-    },
-    "reading": {
-      "anyOf": [
-        {
-          "description": "How to read the risk signal next to others; null outside the catalog",
-          "type": "string"
-        },
-        {
-          "type": "null"
-        }
-      ]
-    },
-    "related_flag": {
-      "anyOf": [
-        {
-          "description": "Detection flag that usually comes with the risk signal",
-          "type": "string"
-        },
-        {
-          "type": "null"
-        }
-      ]
-    },
-    "typical_weight": {
-      "anyOf": [
-        {
-          "maximum": 9007199254740991,
-          "minimum": -9007199254740991,
-          "type": "integer"
-        },
-        {
-          "type": "null"
-        }
-      ]
-    },
-    "weight": {
-      "maximum": 9007199254740991,
-      "minimum": -9007199254740991,
-      "type": "integer"
-    }
-  },
-  "required": [
-    "name",
-    "weight",
-    "label",
-    "meaning",
-    "reading",
-    "typical_weight",
-    "related_flag",
-    "in_catalog"
-  ],
-  "type": "object"
-}

removedOutput schema / properties / signals / type
```
Removed value: -"array"
```

removedOutput schema / properties / source

Removed value: -{
-  "enum": [
-    "history",
-    "webhook",
-    "input"
-  ],
-  "type": "string"
-}

removedOutput schema / properties / truncated

Removed value: -{
-  "description": "Only present (true) when this server shortened the explanation",
-  "type": "boolean"
-}

removedOutput schema / properties / truncation_message

Removed value: -{
-  "description": "What was shortened: risk signals left out, or long pasted values cut",
-  "type": "string"
-}

addedOutput schema / properties / untrusted_data_note
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / weights_available
```
Added value: +{
+  "type": "boolean"
+}
```

changedOutput schema / required

Previous value: -[
-  "request_id",
-  "risk_score",
-  "risk_band",
-  "band_range",
-  "band_meaning",
-  "signals",
-  "detection_flags",
-  "connection_type",
-  "notes",
-  "source"
-]New value: +[
+  "identification_id",
+  "signals",
+  "untrusted_data_note"
+]

First observedv1.0.0Oct 5, 2026

TDQS

B3.4/5.0

Behavior4/5

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

The description adds valuable behavioral context beyond the standard annotations. Specifically, it clarifies that missing signal weights are never zero contribution and that HRE confidence is tracked separately from the final Risk Score, which an AI agent needs to understand the logic of the output.

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 efficient, front-loading the primary function in the first sentence. It avoids unnecessary jargon or fluff, making it easy for an agent to parse the tool's capability quickly.

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?

Given the low schema coverage and the complex domain of risk scoring, the description is sufficiently complete. It addresses the scoring assumptions and input formats sufficiently for an agent to make an informed decision before invoking the tool.

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?

Since schema description coverage is low (25%), the qualitative information provided in the description is very high value. It explains the nature of the input (reading/pasting) and the logic behind the scoring (signal weights, HRE confidence), which the schema omits.

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 title ('Explain Risk Score') and the description clearly state the core function—analyzing an identification for risk. However, the description does not explicitly state what the tool outputs or how this differs structurally from the other ShieldLabs 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 guidance provided on when to use this tool versus alternatives (e.g., if the data is already in a domain or already an identification object). It lacks a clear 'use this when...' statement.

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

Deploy Server