Skip to main content
Glama
Sign In
ams-mcp

ams-mcp

by roykollensvendsen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

ams_now

Read-only

Retrieve live electricity meter readings for current grid draw or export, per-phase volts and amps, and power factor when available.

Instructions

Power used right now. kW drawn from or sent to the grid, each phase's volts and amps, and the power factor when the meter sends one.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, and an output schema documents the return shape, so the description carries a lighter burden. What it usefully adds is the variability caveat that power factor is only present 'when the meter sends one', plus the bidirectional sign meaning of 'drawn from or sent to the grid'; it says nothing about refresh cadence or whether the value is a live sample versus a cached reading.

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?

Two short sentences, front-loaded with the one-line summary followed by the breakdown of returned measurements. No filler and no repetition of the tool name.

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?

For a zero-argument read tool with annotations and an output schema, this is essentially complete: purpose, returned quantities, and the conditional power factor are all covered. Only the freshness/refresh semantics of 'right now' are left unstated.

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 no parameters, so the baseline is 4; there is no argument semantics to explain and the description correctly spends no space on them.

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?

States a specific resource and scope: an instantaneous power reading, with the exact quantities returned (kW import/export, per-phase volts and amps, power factor). The 'right now' framing cleanly separates it from cumulative or historical siblings such as ams_energy or ams_history, though no sibling is named explicitly.

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

Usage Guidelines3/5

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

Usage is only implied by the word 'now' — the agent can infer this is the live snapshot rather than an aggregation or history query, but there is no explicit when-to-use/when-not statement or pointer to an alternative for historical or energy totals.

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