Skip to main content
Glama

route_query

Routes NVIDIA AI questions to the optimal model and reasoning approach by evaluating dependency depth in a knowledge graph.

Instructions

Route an NVIDIA AI question to the optimal model and reasoning approach via graph depth.

The CKG graph IS the router — hop depth is a deterministic complexity metric.
Deeper NVIDIA prerequisite chains (CUDA → TensorRT → TensorRT-LLM → NIM) require
more capable models. No heuristic: the graph decides.

Routing table:
  hop_depth 1  → haiku  · direct          (simple lookup)
  hop_depth 2  → sonnet · generic_cot     (moderate chain)
  hop_depth 3+ → opus   · sparql_cot      (deep dependency, structured reasoning)

Args:
    question: Concept name or natural language question about NVIDIA AI.
    domain:   Domain from list_domains() — e.g. "nvidia-tensorrt-triton", "nvidia-nim".

Returns:
    model_tier + reasoning_approach + why + context subgraph to inject before LLM call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainNo
questionYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description fully explains the deterministic behavior: 'The CKG graph IS the router — hop depth is a deterministic complexity metric.' It details the routing logic and return values. While it does not discuss side effects or permissions, that is acceptable for a query tool.

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?

The description is well-structured and front-loaded with the purpose. While slightly lengthy due to the routing table, every sentence adds value. It could be slightly more concise but remains efficient.

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

Completeness5/5

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

Given the tool's complexity and the absence of schema descriptions, the description is complete: it covers purpose, mechanism, routing table, arguments, and return value. The existence of an output schema is noted, and the description explains the return fields adequately.

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

Parameters5/5

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

The input schema has 0% description coverage, but the description compensates fully by explaining both parameters: 'question: Concept name or natural language question about NVIDIA AI.' and 'domain: Domain from list_domains() — e.g. ...'. This adds essential meaning beyond the schema.

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

Purpose5/5

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

The description clearly states the tool's purpose: 'Route an NVIDIA AI question to the optimal model and reasoning approach via graph depth.' It identifies the specific verb (route) and resource (NVIDIA AI question), and the detailed routing table distinguishes it from sibling tools that handle different aspects of ecosystem queries.

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

Usage Guidelines4/5

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

The description provides strong context for when to use this tool by explaining the deterministic graph depth logic and routing table. However, it does not explicitly contrast with sibling tools like 'ask_nvidia' or 'search_concepts', which would fully clarify when this is the optimal choice.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/WangHuikong/ckg-nvidia-ai'

If you have feedback or need assistance with the MCP directory API, please join our Discord server