# get_best_model_for_query

A read tool on the DeepMyst MCP Server MCP server.

Agent View of the PolicyLayer registry record for `get_best_model_for_query`. HTML page: https://policylayer.com/tools/deepmyst-deepmyst-mcp/get-best-model-for-query

## Facts

- Tool: `get_best_model_for_query`
- Server: DeepMyst MCP Server (`deepmyst/deepmyst-mcp`) — https://policylayer.com/tools/deepmyst-deepmyst-mcp.md
- Homepage: https://github.com/DeepMyst/DeepMyst-MCP
- Risk category: Read (Low risk)
- Registry record: grade B, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_best_model_for_query",
    "arguments": {}
  }
}
```

## Why get_best_model_for_query is rated Low

This tool appears to select or recommend a model based on a query, which is fundamentally a read operation—it queries state and returns information without modifying, executing, or deleting anything. The server's purpose is LLM routing and optimization, implying the tool evaluates and returns model recommendations.

From the tool's own definition: "Tool name 'get_best_model_for_query' and server description indicate this retrieves or queries information about the best model to use for a given query. No description provided, but the name and context suggest data retrieval with no side effects."

## Use case

AI agents call get_best_model_for_query to retrieve information from DeepMyst MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches DeepMyst MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_best_model_for_query": {}
  }
}
```

## Other tools on DeepMyst MCP Server (4)

- `auto_routed_completion` — Execute — https://policylayer.com/tools/deepmyst-deepmyst-mcp/auto-routed-completion.md
- `smart_completion` — Execute — https://policylayer.com/tools/deepmyst-deepmyst-mcp/smart-completion.md
- `deepmyst_completion` — Read — https://policylayer.com/tools/deepmyst-deepmyst-mcp/deepmyst-completion.md
- `optimized_completion` — Read — https://policylayer.com/tools/deepmyst-deepmyst-mcp/optimized-completion.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=deepmyst-deepmyst-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/deepmyst-deepmyst-mcp