Skip to main content
Glama
Sign In
LLMxRay-MCP

LLMxRay-MCP

by LogneBudo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Read LLMxRay status

read_llmxray_status
Read-onlyIdempotent

Reads LLMxRay server status: observe port, forwarded Ollama version, retained turns, disk text policy, and start time. Use when no turns appear or to confirm which Ollama your calls reach.

Instructions

Where LLMxRay runs and what it holds: the observe port and whether it listens, the Ollama it forwards to and its version, how many turns are kept of the 500 it holds, whether request text is kept on disk, and when it started. Use it first when diagnose_my_turns or read_my_last_turn answers that nothing was seen, or to confirm which Ollama your calls reach. Those tools read the turns; this one reads the server itself. Takes no arguments. Nothing can be changed through MCP; settings live on the Live page. Needs LLMxRay running (npx llmxray); if it is not reachable the answer says so and names the URL tried. Under a second.

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": "read_llmxray_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.8.6

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses that nothing can be mutated through MCP, that settings live on the Live page, that LLMxRay must be running (npx llmxray), that failures name the URL tried, and that it responds in under a second. This is genuine operational context an agent cannot infer from the annotations.

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

Conciseness5/5

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

Front-loaded with the return payload, then usage routing, then constraints and latency. Every sentence is load-bearing: the field list defines scope, the sibling comparison routes selection, and the failure/latency notes set expectations.

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?

There is no output schema, so the description carries the return-value burden and does so by enumerating the status fields. Requirements, prerequisites, failure behavior, and latency are all covered, leaving nothing an agent needs to call this correctly.

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

Parameters4/5

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

The tool takes zero arguments, so the baseline is 4. The description reinforces this with 'Takes no arguments', which is a useful confirmation but adds little semantic depth beyond an empty 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 opening sentence names a specific verb (reads) and enumerates the exact resources returned: observe port and listen state, Ollama target and version, turn retention, disk retention of request text, start time. The line 'Those tools read the turns; this one reads the server itself' cleanly differentiates it from diagnose_my_turns and read_my_last_turn.

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

Usage Guidelines5/5

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

It explicitly states when to reach for it ('Use it first when diagnose_my_turns or read_my_last_turn answers that nothing was seen') and the alternative goal ('to confirm which Ollama your calls reach'), naming the competing siblings and the diagnostic condition that selects this tool.

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

Deploy Server

Other Tools