Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed to call tool from openapi-mcp-server #244587

Closed
deepak1556 opened this issue Mar 25, 2025 · 6 comments
Closed

Failed to call tool from openapi-mcp-server #244587

deepak1556 opened this issue Mar 25, 2025 · 6 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug

Comments

@deepak1556
Copy link
Collaborator

Testing #244522

"openapi-server": {
            "command": "npx",
            "args": ["C:\\Users\\demohan\\github\\openapi-mcp-server", "run"],
        },
  • Try a query like find information about the openai api and see the tool getApiOverview invoked
  • Now try the same with explicit call #getApiOverview find information about the openai api
Failed to compute args for tool: "9f1_getApiOverview"
@connor4312
Copy link
Member

This is an artefact of letting MCP tools be able to be referenced in the prompt even if the model can't always figure out their args. Not sure what we should do here, should be treat failures to compute args a warning rather than a failure?

@connor4312 connor4312 added the under-discussion Issue is under discussion for relevance, priority, approach label Mar 25, 2025
@roblourens
Copy link
Member

even if the model can't always figure out their args

What does that mean? What did the model generate?

@connor4312
Copy link
Member

The "Failed to compute args for tool" comes from copilot when it tries to fill in the arguments for a tool reference

@roblourens
Copy link
Member

Yeah but from the code it looks like we made a request, and tried to force the tool call, but it came back with a response that didn't include a tool call right? So what did it do?

@connor4312
Copy link
Member

Ah, I can repro, and that was actually hiding a 400 error. It was the string length limit. I need to apply schema normalization separately to the references call clearly. Sorry for the false assignment.

@connor4312 connor4312 added bug Issue identified by VS Code Team member as probable bug and removed under-discussion Issue is under discussion for relevance, priority, approach labels Mar 25, 2025
@roblourens
Copy link
Member

I see, we should also make sure that Failed to compute args doesn't hide a request failure, I see that it's a dumb check

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue identified by VS Code Team member as probable bug
Projects
None yet
Development

No branches or pull requests

4 participants