Skip to main content
Glama
Sign In
ApexMCP

ApexMCP

by mad-science-lab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

apex_water_parameters

Retrieves current aquarium water parameters—temperature, pH, ORP, salinity, alkalinity, calcium, magnesium, nitrate, and phosphate—in one concise response.

Instructions

Temp, pH, ORP, salinity and any Trident chemistry (alk, Ca, Mg, NO3, PO4) in one short answer.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It hints at a compact read-only snapshot ('in one short answer') and that Trident chemistry is conditional ('any'), but says nothing about units, staleness of readings, behavior when a probe is missing, or auth needs.

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?

One short sentence that front-loads the returned values and ends with the format promise. Nothing is padded and nothing essential is buried.

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?

With an output schema present, return values need no explanation and there are no parameters to document, so the core is covered. What remains missing is the selection context against the probe-oriented siblings and any note on reading freshness or units.

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 parameters, so the baseline is 4; the description correctly implies no inputs are needed to retrieve the full parameter set.

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?

The description enumerates exactly what the tool returns — temp, pH, ORP, salinity and Trident chemistry (alk, Ca, Mg, NO3, PO4) — so the resource is unambiguous. It implicitly contrasts with narrow siblings like apex_get_probes or apex_probe_history by being the consolidated snapshot, but never names them.

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 explicit when-to-use guidance and no mention of alternatives, even though apex_get_probes, apex_probe_history and apex_probe_stats occupy overlapping territory. An agent must infer that this is the quick 'give me everything at once' call.

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