Skip to main content
Glama
Sign In
ApexMCP

ApexMCP

by mad-science-lab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

apex_digital_inputs

Monitor aquarium equipment by reading digital input states (OPEN/CLOSED) from float switches and other sensors on Neptune Apex controllers.

Instructions

Float switches and other digital inputs as OPEN or CLOSED.

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

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/5.0
Behavior2/5

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

With no annotations, the description bears full responsibility for behavioral disclosure. It conveys the return values but does not state that this is a read-only operation, nor does it mention any permissions, rate limits, or side effects. For a simple getter this is a minor gap, but it remains an omission.

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, short phrase with no wasted words. It is front-loaded with the subject, but the lack of a complete sentence makes it slightly less structured than an ideal definition.

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

Completeness4/5

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

Given that the tool has no parameters and an output schema exists, the description provides enough information for an agent to know what the tool returns (OPEN/CLOSED states of digital inputs). However, it could be more complete by explicitly stating the read-only nature and its place among sibling tools.

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 score is 4. The description does not need to explain parameter usage, and it appropriately adds no parameter-related content.

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 identifies the resource (float switches and other digital inputs) and the values returned (OPEN or CLOSED), but it is a noun phrase without an explicit verb, leaving the action (presumably 'get') implied rather than stated. It does not explicitly differentiate from siblings, though the subject matter is distinct from probes, outlets, etc.

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?

No guidance is provided on when to use this tool versus alternatives. The description merely states what data it returns, without any context about prerequisites, filtering, or when an agent should choose this over other apex tools.

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