Skip to main content
Glama
Sign In
MystoraX MCP Server

MystoraX MCP Server

by Daneshpajouh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

mystorax_science_status

Check the current readiness of the Science OS and Axiom system, along with the MCP proxy connection status, to determine if the environment is prepared for operational use.

Instructions

Science OS / Axiom readiness + MCP proxy status.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.1.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It indicates this is a read-oriented status operation and mentions 'readiness' and 'proxy status', but gives no detail on what readiness means, what the status output covers, or any side effects. It adds modest context but is thin for an unannotated 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 a single concise clause, well under a sentence, with zero wasted words. It's appropriately sized for a status tool, though TLA-heavy language (OS, Axiom, MCP) slightly hurts readability for agents unfamiliar with the domain.

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?

For a zero-parameter, no-output-schema status tool, the description is serviceable but could be richer. It doesn't explain what the response contains (readiness flags, proxy health, versions) or how it relates to the mystorax_axiom_* and mystorax_science_* siblings, which limits agent confidence in using it.

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 tool has 0 parameters and 100% schema coverage by default (no parameters to describe). The absence of parameters means the description adds no needed parameter detail; this is the correct baseline for a zero-parameter tool.

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

Purpose3/5

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

The description 'Science OS / Axiom readiness + MCP proxy status' conveys a clear status-check purpose with a verb+resource shape. However, it doesn't explicitly say it reports/displays status, and it gives no differentiation from siblings like mystorax_job_status or mystorax_science_resume.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no exclusions, and no mention of alternatives. Given six sibling tools, the description offers no roadmap for when to choose this status tool over mystorax_job_status or mystorax_axiom_tool_search.

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