Skip to main content
Glama

Query Nexus

query_nexus

Send GET or POST requests to the local Nexus OpenAI-compatible gateway path to fetch model lists or chat completions and return the JSON response or an error.

Instructions

Call the Nexus OpenAI-compatible gateway with a path. Use list_models with backend=nexus for model names. Local HTTP. Returns the gateway JSON or an error.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
dataNoJSON body for POST. Omit for GET.
pathNoGateway path such as /v1/models or /v1/chat/completions. Default /v1/models./v1/models
methodNoHTTP method. GET or POST. Default GET.GET

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv6.2.1
    • addedInput schema / properties / data / description
      Added value: +"JSON body for POST. Omit for GET."
    • addedInput schema / properties / method / description
      Added value: +"HTTP method. GET or POST. Default GET."
    • addedInput schema / properties / path / description
      Added value: +"Gateway path such as /v1/models or /v1/chat/completions. Default /v1/models."
  2. Addedv6.1.5

TDQS

B3.4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, so the agent knows this is a potentially state-changing, network-touching call. The description adds 'Local HTTP' and states it returns gateway JSON or an error, which is real context. It does not disclose that POST calls may mutate gateway or model state, nor any auth or error-shape details.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short, front-loaded sentences with no filler; the core action comes first, followed by the discovery hint, transport note, and return behavior. The telegraphic fragments ('Local HTTP.') are terse but each carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return value detail isn't required, and all three parameters are documented. What is missing is the operational context an agent needs for a free-form open-world gateway call: mutation risk on POST, expected error behavior, and how it differs from the other proxy/query siblings.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so path, data, and method are already fully documented in the schema. The description only echoes 'with a path' and doesn't add constraints, accepted path forms, or POST/GET semantics beyond what the schema states. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: calling the Nexus OpenAI-compatible gateway with a path. It also distinguishes itself from a sibling by directing model-name lookups to list_models with backend=nexus. It stops short of saying what the gateway is for relative to query_vibe_proxy or query_local_ai_service.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives one concrete routing hint (use list_models with backend=nexus for model names), which is genuinely useful. However, it never says when to use this tool instead of the several sibling gateway/proxy query tools (query_vibe_proxy, query_local_ai_service, chat_with_model), and gives no prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.