partner-center-mcp

Decode a raw error response

pc_decode_error

Read-onlyIdempotent

Decode a raw Partner Center error response: extract the error code, HTTP status, and correlation ID, and get documented causes, fixes, and support-request wording.

Instructions

Take a raw Partner Center error response and decode it: extract the error code, HTTP status, and MS-CorrelationId, then return the documented causes, remediation, likely scenarios, and the exact wording to quote in a support request. This is the right first tool when something failed and you have the response in hand. Use pc_lookup_error instead when you have already isolated a clean code, and pc_diagnose when you only have a prose description with no response body. Read-only, offline, deterministic parsing — the input is never sent anywhere and no request is replayed. Always returns ok:true: an unrecognised code still yields the parsed fields, status-based candidates, and a note on what to try next.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`error`	Yes	The error response pasted verbatim — a JSON body such as {"code":"900400","description":"..."}, or unstructured log text containing the failure. Include the response headers if you have them so the MS-CorrelationId can be recovered. Partial or malformed input is handled: whatever cannot be parsed is reported as null.

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes	True when the call succeeded and `data` is populated; false when `error` explains why not.
`data`	No	The result payload. Present only when `ok` is true.
`error`	No	Human-readable reason the call failed. Present only when `ok` is false.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.13.0Aug 1, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

addedInput schema / properties / error / description

Added value: +"The error response pasted verbatim — a JSON body such as {\"code\":\"900400\",\"description\":\"...\"}, or unstructured log text containing the failure. Include the response headers if you have them so the MS-CorrelationId can be recovered. Partial or malformed input is handled: whatever cannot be parsed is reported as null."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "data": {
+      "additionalProperties": false,
+      "description": "The result payload. Present only when `ok` is true.",
+      "properties": {
+        "candidatesByStatus": {
+          "description": "Fallback shortlist keyed off the HTTP status, populated only when no exact code match was found.",
+          "items": {
+            "additionalProperties": false,
+            "properties": {
+              "description": {
+                "description": "What that code means.",
+                "type": "string"
+              },
+              "errorCode": {
+                "description": "A code that shares the extracted HTTP status.",
+                "type": "string"
+              }
+            },
+            "required": [
+              "errorCode",
+              "description"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "correlationGuidance": {
+          "description": "Ready-to-use sentence for a support request, or instructions for capturing the correlation id when it was missing.",
+          "type": "string"
+        },
+        "match": {
+          "anyOf": [
+            {
+              "additionalProperties": false,
+              "properties": {
+                "causes": {
+                  "description": "Known conditions that trigger it.",
+                  "items": {
+                    "type": "string"
+                  },
+                  "type": "array"
+                },
+                "description": {
+                  "description": "What the error means.",
+                  "type": "string"
+                },
+                "docUrl": {
+                  "description": "Microsoft Learn page covering this error.",
+                  "format": "uri",
+                  "type": "string"
+                },
+                "errorCode": {
+                  "description": "Partner Center error code, e.g. \"900400\".",
+                  "type": "string"
+                },
+                "httpStatus": {
+                  "description": "HTTP status code the API returns with this error.",
+                  "type": "number"
+                },
+                "relatedScenarios": {
+                  "description": "Scenario ids where this error commonly surfaces.",
+                  "items": {
+                    "type": "string"
+                  },
+                  "type": "array"
+                },
+                "remediation": {
+                  "description": "Concrete fix to apply.",
+                  "type": "string"
+                }
+              },
+              "required": [
+                "httpStatus",
+                "errorCode",
+                "description",
+                "causes",
+                "remediation",
+                "docUrl"
+              ],
+              "type": "object"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "The documented error entry for the extracted code, or null when the code is unknown or absent."
+        },
+        "note": {
+          "description": "Present when decoding was incomplete, explaining what to do next.",
+          "type": "string"
+        },
+        "parsed": {
+          "additionalProperties": false,
+          "description": "What was extracted from the raw input.",
+          "properties": {
+            "code": {
+              "anyOf": [
+                {
+                  "type": "string"
+                },
+                {
+                  "type": "null"
+                }
+              ],
+              "description": "Error code recovered from the input, or null if none could be found."
+            },
+            "correlationId": {
+              "anyOf": [
+                {
+                  "type": "string"
+                },
+                {
+                  "type": "null"
+                }
+              ],
+              "description": "MS-CorrelationId GUID recovered from the input, or null. Microsoft support needs this to trace the request."
+            },
+            "httpStatus": {
+              "anyOf": [
+                {
+                  "type": "number"
+                },
+                {
+                  "type": "null"
+                }
+              ],
+              "description": "HTTP status recovered from the input, or null."
+            }
+          },
+          "required": [
+            "code",
+            "httpStatus",
+            "correlationId"
+          ],
+          "type": "object"
+        },
+        "relatedScenarios": {
+          "description": "Operations where this error commonly appears. Empty when there was no match.",
+          "items": {
+            "additionalProperties": false,
+            "properties": {
+              "docUrl": {
+                "description": "Microsoft Learn page documenting this operation.",
+                "type": "string"
+              },
+              "id": {
+                "description": "Scenario id to pass to pc_get_scenario or pc_generate_call.",
+                "type": "string"
+              },
+              "title": {
+                "description": "Human-readable name of the operation.",
+                "type": "string"
+              }
+            },
+            "required": [
+              "id",
+              "title",
+              "docUrl"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        }
+      },
+      "required": [
+        "parsed",
+        "match",
+        "relatedScenarios",
+        "candidatesByStatus",
+        "correlationGuidance"
+      ],
+      "type": "object"
+    },
+    "error": {
+      "description": "Human-readable reason the call failed. Present only when `ok` is false.",
+      "type": "string"
+    },
+    "ok": {
+      "description": "True when the call succeeded and `data` is populated; false when `error` explains why not.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "ok"
+  ],
+  "type": "object"
+}

Addedv0.6.0Jun 22, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the annotations (readOnlyHint, idempotentHint, destructiveHint), the description discloses that the tool is offline and deterministic, never sends input anywhere, and never replays requests. It also explains the edge-case behavior of always returning ok:true with parsed fields and a note for unrecognized codes. This adds behavioral context well beyond what annotations provide.

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 dense but every sentence earns its place: purpose, usage trigger, alternatives, behavioral guarantees, and return behavior. It is front-loaded with the core purpose and uses concise language without redundancy.

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 tool's complexity (handles raw, partial, or malformed input) and that an output schema exists, the description nevertheless covers input expectations, output guarantees (always ok:true), and follow-up guidance (note with next steps). It is fully self-contained for an agent to decide when and how to invoke it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% coverage, with a detailed description of the 'error' parameter covering verbatim input, JSON or unstructured text, headers, and malformed input handling. The tool description itself does not add significant meaning about the parameter beyond what the schema already states, so baseline 3 is appropriate.

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 opens with a specific verb ('decode') and resource ('raw Partner Center error response'), and details exactly what is extracted (error code, HTTP status, MS-CorrelationId) and returned (causes, remediation, scenarios, support wording). It explicitly distinguishes from sibling tools like pc_lookup_error and pc_diagnose, making the tool's unique role unambiguous.

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?

It states the intended usage context: 'the right first tool when something failed and you have the response in hand.' It also provides clear exclusion criteria by naming alternatives (use pc_lookup_error when you have a clean code, pc_diagnose when you have only a prose description). This is textbook when-to-use guidance.

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