partner-center-mcp

Look up an error code

pc_lookup_error

Read-onlyIdempotent

Look up Partner Center errors by numeric code or HTTP status to get the meaning, known causes, remediation, and documentation link.

Instructions

Look up a Partner Center error by its numeric code or HTTP status and return what it means, its known causes, the remediation, the doc link, and the scenarios where it usually appears. Use this when you already have a clean code. If you have a raw error response, pc_decode_error is better — it extracts the code and correlation id for you first. For a symptom described in prose with no code at all, use pc_diagnose. Read-only, offline, deterministic. Exactly one of code or httpStatus must be supplied; supplying neither returns ok:false. An unknown code returns ok:false with suggestions listing every code in the pack.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`code`	No	Partner Center error code as a string, e.g. "900400" or "20002". Matched exactly, so strip surrounding text first. Takes precedence when both this and `httpStatus` are given. Supply this or `httpStatus`.
`httpStatus`	No	HTTP status code to list errors for, e.g. 400 or 403. Use this when you have no Partner Center code — it returns every documented error with that status, so expect several. Ignored when `code` is supplied. Supply this or `code`.

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.
`suggestions`	No	Valid values to retry with, returned alongside `error` when the requested identifier was not found.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv0.13.0Aug 1, 2026

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

addedInput schema / properties / code / description

Added value: +"Partner Center error code as a string, e.g. \"900400\" or \"20002\". Matched exactly, so strip surrounding text first. Takes precedence when both this and `httpStatus` are given. Supply this or `httpStatus`."

addedInput schema / properties / httpStatus / description

Added value: +"HTTP status code to list errors for, e.g. 400 or 403. Use this when you have no Partner Center code — it returns every documented error with that status, so expect several. Ignored when `code` is supplied. Supply this or `code`."

addedInput schema / properties / httpStatus / maximum
```
Added value: +9007199254740991
```
addedInput schema / properties / httpStatus / minimum
```
Added value: +-9007199254740991
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "data": {
+      "anyOf": [
+        {
+          "additionalProperties": false,
+          "description": "The single matching error, returned for a `code` lookup.",
+          "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": "Scenarios where this error commonly surfaces, resolved from ids to { id, title, docUrl }.",
+              "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"
+            },
+            "remediation": {
+              "description": "Concrete fix to apply.",
+              "type": "string"
+            }
+          },
+          "required": [
+            "httpStatus",
+            "errorCode",
+            "description",
+            "causes",
+            "remediation",
+            "docUrl",
+            "relatedScenarios"
+          ],
+          "type": "object"
+        },
+        {
+          "description": "Every documented error with the requested status, returned for an `httpStatus` lookup.",
+          "items": {
+            "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": "array"
+        }
+      ],
+      "description": "The result payload. Present only when `ok` is true."
+    },
+    "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"
+    },
+    "suggestions": {
+      "description": "Valid values to retry with, returned alongside `error` when the requested identifier was not found.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "ok"
+  ],
+  "type": "object"
+}

First observedv0.1.0Jun 19, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint; the description adds 'offline, deterministic' and details the ok:false cases (missing both params, unknown code with suggestions). This goes beyond the annotations, informing the agent about side-effect-free, repeatable behavior.

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?

Four sentences with no filler; front-loads the core function, then gives alternatives and constraints. Every sentence earns its place.

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?

For a two-parameter lookup tool with a rich output schema and strong annotations, the description covers use cases, alternatives, edge cases, and failure modes. No significant gaps remain.

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?

The schema already provides 100% coverage of both parameters. The description adds the exclusive-or rule that exactly one must be supplied and mentions the precedence and unknown-code suggestions, which are not in the schema. Since the schema is thorough, the extra value is moderate but meaningful.

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 uses a specific verb ('Look up') with a clear resource ('Partner Center error') and enumerates the returned fields (meaning, causes, remediation, doc link, scenarios). It explicitly distinguishes from siblings by naming pc_decode_error and pc_diagnose, so the agent knows exactly when this tool is appropriate.

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?

States 'Use this when you already have a clean code' and provides explicit alternatives for raw responses (pc_decode_error) and prose symptoms (pc_diagnose). It also specifies the input constraint (exactly one of code/httpStatus) and the failure behavior, giving clear operational guidance.

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