fix: allow tool call even when server name prefix is missing

[uc4w6c]

Title

fix: allow tool call even when server name prefix is missing

Relevant issues

Fixes #14986
Fixes #15364
Fixes #16381

Related #15352

Pre-Submission checklist

Please complete all items before asking a LiteLLM maintainer to review your PR

• I have Added testing in the tests/litellm/ directory, Adding at least 1 test is a hard requirement - see details
• I have added a screenshot of my new test passing locally
• My PR passes all unit tests on make test-unit
• My PR's scope is as isolated as possible, it only solves 1 specific problem

Type

🐛 Bug Fix
✅ Test

Changes

https://www.loom.com/share/b177e2ff18e5476d9904f101988f8bc2

[vercel]

@uc4w6c is attempting to deploy a commit to the CLERKIEAI Team on Vercel.

A member of the Team first needs to authorize it.

[krrishdholakia]

seems like this fails on testing @uc4w6c

can you either update the test or fix if there's an underlying issue?

[uc4w6c]

@krrishdholakia
Thanks, I've fixed it.

[rromanchuk]

Related/Unrelated

I have no real grasp how logs work and it looks like they are getting wrapped up in observability as a premium offering. I give up immediately when trying to file a potentially useful ticket because the amount of time it takes for information gathering. I have a mixture of 3-4 deprecated configs, process flags, and env vars and perform a rain dance in hopes of a trace.

UI

Tailing STDOUT/ERROR 😭

LLM Response

These 403 errors show up everywhere (like the output of an LLM), except for ?page=logs, and it's rage inducing. Intuitively I assume these are just regressions from enterprise features and directly related to the date uv run litellm was ran. Whatever the issue I hit, it is particularly obnoxious because all GET/list functionality work fine but the tool call fails, so it wasn't until running get_current_time to realize this was a LiteLLM artifact, not mcp server issue.

Also WHAT IS THIS 😭 Is the advice accurate? Why are those keys related to title? Are there any exceptions? I would like request and response payloads 😭

const hasMessages =
  row.original.messages &&
  (Array.isArray(row.original.messages)
    ? row.original.messages.length > 0
    : Object.keys(row.original.messages).length > 0);

const hasResponse =
  row.original.response && Object.keys(formatData(row.original.response)).length > 0;

const missingData = !hasMessages && !hasResponse;

Asserted somewhere? Why not check the actual config keys? Enterprise artifact?

[uc4w6c]

@rromanchuk
I’m sorry for the inconvenience.
It should be resolved in PR: #16695, so please give it another try.