Skip to content

Commit 1968066

Browse files
committed
Peer review
1 parent c135a4c commit 1968066

4 files changed

+9
-17
lines changed

assemblies/assembly-resolving-common-problems-with-mcp-clients-and-tools.adoc

Lines changed: 0 additions & 14 deletions
This file was deleted.

assemblies/assembly-troubleshooting-mcp-server-and-client-problems.adoc

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,10 +4,16 @@
44
= Troubleshooting MCP server and client problems
55
:context: assembly-troubleshooting-mcp-server-and-client-problems
66

7+
The following procedures guide you through resolving common issues when using a Model Communication Protocol (MCP) server and tool.
8+
79
include::modules/model-context-protocol-tools/proc-verifying-successful-installation-of-mcp-plugins.adoc[leveloffset=+1]
810

911
include::modules/model-context-protocol-tools/proc-checking-logs-for-mcp-tool-execution-and-errors.adoc[leveloffset=+1]
1012

1113
include::modules/model-context-protocol-tools/con-understand-and-respond-to-mcp-tool-error-messages.adoc[leveloffset=+1]
1214

13-
include::assembly-resolving-common-problems-with-mcp-clients-and-tools.adoc[leveloffset=+1]
15+
include::modules/model-context-protocol-tools/proc-resolving-the-model-does-not-support-tool-calling-error.adoc[leveloffset=+1]
16+
17+
include::modules/model-context-protocol-tools/proc-resolving-authentication-issues-when-tool-are-not-found.adoc[leveloffset=+1]
18+
19+
include::modules/model-context-protocol-tools/proc-nonsensical-mcp-tool-output.adoc[leveloffset=+1]

modules/model-context-protocol-tools/proc-checking-logs-for-mcp-tool-execution-and-errors.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
:_mod-docs-content-type: PROCEDURE
22

33
[id="proc-checking-logs-for-mcp-tool-execution-and-errors.adoc_{context}"]
4-
= Checking logs for MCP tool execution and errors
4+
= Checking MCP tool logs for status and errors
55

66
The {backstage} `LoggerService` target name starts with the name of the MCP tool (either `software-catalog-mcp-tool` or `techdocs-mcp-tool`). The MCP tools generate a log by default. For example:
77

modules/model-context-protocol-tools/proc-resolving-authentication-issues-when-tool-are-not-found.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ If your MCP client connects to the server but cannot find deployed tools, an aut
88
.Procedure
99

1010
. Verify the authentication token.
11-
.. Configure a static token for the RHDH MCP server.
11+
.. Configure a static token for the {product-very-short} MCP server.
1212
.. Set this token as the bearer token in your MCP client and make sure the authorization header is the configuration specifies `Bearer` before the token, for example, `Bearer <mcp_token>`.
1313
. Check the MCP endpoint configuration.
1414
.. Confirm that the MCP server URL properly resolves, particularly if you are using a desktop client.

0 commit comments

Comments
 (0)