examples(mcp): make example more robust to LLM hallucination

[willkill07]

Description

• Explicitly specify timezone in MCP tool description.
• Add note in example README.

Closes

By Submitting this PR I confirm:

• I am familiar with the Contributing Guidelines.
• We require that all contributors "sign-off" on their commits. This certifies that the contribution is your original work, or you have rights to submit it under the same license, or a compatible license.
  • Any contribution which contains commits that are not Signed-Off will not be accepted.
• When the PR is ready for review, new or existing tests cover these changes.
• When the PR is ready for review, the documentation is up to date with these changes.

Summary by CodeRabbit

• Documentation
  • Clarified timezone handling guidance for the MCP time tool to explicitly indicate America/Los_Angeles timezone usage across related configuration materials.

[coderabbitai]

Walkthrough

The changes update documentation and configuration descriptions for the MCP time tool to clarify that the timezone should always be set to America/Los_Angeles when calling the function. No functional modifications or new features are introduced.

Changes

Cohort / File(s)	Summary
Configuration Files examples/MCP/simple_calculator_mcp/configs/config-mcp-client.yml, examples/MCP/simple_calculator_mcp/configs/config-per-user-mcp-client.yml	Updated the description for the get_current_time tool override under mcp_time function group to include guidance: "Always pass in the timezone as America/Los_Angeles".
Documentation examples/MCP/simple_calculator_mcp/README.md	Updated the narrative to reflect that the mcp_time tool description now includes the timezone assumption of America/Los_Angeles.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main objective of the PR: making the MCP example more robust by reducing LLM hallucination through explicit timezone specification.
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

Tip

Try Coding Plans. Let us write the prompt for your AI agent so you can ship faster (with fewer bugs).
Share your feedback on Discord.

---

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

[AnuradhaKaruppiah]

Looks great. ty for taking care of it.

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

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

Inline comments:
In `@examples/MCP/simple_calculator_mcp/README.md`:
- Line 92: The README's mcp_time description and the YAML config descriptions
are inconsistent about timezone handling; update the YAML descriptions (the
entries that currently read "Always pass in the timezone as
America/Los_Angeles") to match the README's accurate server-configured wording
by changing them to indicate the timezone is assumed/forced to
America/Los_Angeles (e.g., "Timezone is assumed to be America/Los_Angeles"), and
ensure the mcp_time description in the README remains aligned with that phrasing
so both README and YAML convey the same "assumed" behavior.

---

ℹ️ 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 3f27f98 and fa04ce0.

📒 Files selected for processing (3)

• examples/MCP/simple_calculator_mcp/README.md
• examples/MCP/simple_calculator_mcp/configs/config-mcp-client.yml
• examples/MCP/simple_calculator_mcp/configs/config-per-user-mcp-client.yml

[willkill07]

/merge