Skip to main content
Glama
Sign In
ApexMCP

ApexMCP

by mad-science-lab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

apex_get_outlets

Retrieve all Neptune Apex outlets with mode, power state, power level, and pump mode to monitor connected aquarium equipment.

Instructions

Every outlet with mode (AUTO/ON/OFF), whether it is energized, power level and pump mode.

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_get_outlets"
  }
}

Input Schema

NameRequiredDescriptionDefault
outlet_typeNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It lists returned outlet attributes but does not state that the operation is read-only, whether it has side effects, how pagination or rate limits work, or any authorization requirements.

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 tight sentence with no wasted words and front-loads the outlet resource. Its brevity is appropriate, though the lack of a verb contributes to the clarity gaps noted elsewhere.

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

Completeness2/5

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

Although an output schema exists, the tool has no annotations and its only input parameter is undocumented in both schema and description. This leaves the agent unable to determine how outlet_type affects the result or when filtering is appropriate.

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

Parameters1/5

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

The sole optional parameter, outlet_type, has 0% schema description coverage and is never mentioned in the description. Its meaning, accepted values, and filtering behavior are completely undocumented.

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 phrase 'Every outlet with mode...' identifies the resource and lists returned attributes, but it lacks an explicit retrieval verb and does not distinguish this tool from siblings such as apex_outlet_events. An agent can infer it lists outlets, but the purpose is only implied rather than crisply stated.

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 guidance on when to use this tool versus alternatives like apex_outlet_events or apex_power_summary. It also does not explain when to supply outlet_type or when to omit it.

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