Doc stuff

[Akrog]

Description

Small doc improvements:

• One of the Authorization examples incorrectly indicates that the file should have the Bearer section when it shouldn't.
• There is no mention of how in run.yaml under thee tool_runtime there's a need for the mcp remote provider.

Type of change

• Documentation Update

Tools used to create PR

Manually written.

Summary by CodeRabbit

• Documentation
  • Expanded tool configuration documentation with detailed setup instructions
  • Added comprehensive MCP server configuration guide covering authentication methods (tokens, Kubernetes, OAuth) and header propagation
  • Enhanced example configurations demonstrating vector store and MCP tool integration
  • Improved authentication token sample output formatting

[coderabbitai]

Walkthrough

Documentation expanded to explain MCP server configuration, authentication methods (static tokens, Kubernetes, OAuth, client-provided tokens), and header propagation behavior. Example run.yaml updated with MCP tool provider configuration and vector store identification.

Changes

Cohort / File(s)	Summary
Documentation & Configuration README.md	Expanded MCP Servers section with configuration structure, authentication methods (static tokens, Kubernetes, OAuth, client-provided tokens), header propagation rules, and comprehensive examples for various auth scenarios and server discovery.
Example Configuration examples/run.yaml	Added model-context-protocol provider entry under tool_runtime and augmented vector store configuration with explicit vector_store_id identifier.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Possibly related PRs

• LCORE-1280: Updated code docs #1083 — Coordinates documentation changes for MCP server authentication and header handling alongside configuration examples.
• LCORE-1366: Fixed MCP "Authorization" header not using the authorization parameter #1203 — Documents MCP authorization field changes corresponding to the authorization/header propagation behavior covered in this PR's documentation.
• LCORE-169: Provide initial set of opinionated & tested llama-stack co… #424 — Similarly adds and enables the model-context-protocol tool_runtime provider in README and example run.yaml configurations.

Suggested reviewers

• tisnik
• VladimirKadlec
• matysek

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'Doc stuff' is vague and generic, using a non-descriptive term that fails to convey the specific changes being made.	Replace with a more specific title like 'Fix Authorization example and document MCP tool_runtime configuration' to clearly describe the actual changes.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

🧹 Nitpick comments (1)

README.md (1)

333-340: Consider adding providers: context to the YAML snippet for copy/paste safety.

The snippet is correct, but showing it nested under providers: would reduce misconfiguration risk for readers skimming the section.

Suggested doc tweak

-```yaml
-  tool_runtime:
-    - provider_id: model-context-protocol
-      provider_type: remote::model-context-protocol
-      config: {}
-```
+```yaml
+providers:
+  tool_runtime:
+    - provider_id: model-context-protocol
+      provider_type: remote::model-context-protocol
+      config: {}
+```

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@README.md` around lines 333 - 340, Update the YAML example so it's shown
nested under a top-level providers context to avoid copy/paste misconfiguration:
modify the snippet that contains tool_runtime and provider_id:
model-context-protocol (and provider_type: remote::model-context-protocol,
config: {}) to be indented under a new providers: key, i.e. wrap the existing
tool_runtime block inside providers:, ensuring indentation matches the
surrounding examples and the keys tool_runtime, provider_id, provider_type, and
config remain unchanged.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@README.md`:
- Around line 333-340: Update the YAML example so it's shown nested under a
top-level providers context to avoid copy/paste misconfiguration: modify the
snippet that contains tool_runtime and provider_id: model-context-protocol (and
provider_type: remote::model-context-protocol, config: {}) to be indented under
a new providers: key, i.e. wrap the existing tool_runtime block inside
providers:, ensuring indentation matches the surrounding examples and the keys
tool_runtime, provider_id, provider_type, and config remain unchanged.

---

ℹ️ Review info

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f0647c7 and 1c3392b.

📒 Files selected for processing (2)

• README.md
• examples/run.yaml

[tisnik]

LGTM