Skip to main content
Glama
Sign In
ams-mcp

ams-mcp

by roykollensvendsen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

ams_history

Read-only

Retrieves home electricity meter history for today or the current month, including energy used so far, busiest hour or day, and last month's totals.

Instructions

A day or month in short. Period 'day' (the default): today so far and its busiest hour. 'month': this month so far, its busiest day, and last month.

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

Input Schema

NameRequiredDescriptionDefault
periodNoday

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

readOnlyHint=true already covers the safety profile, and the description adds the concrete scope of what is returned for each period. It omits things like timezone handling, whether data is live or cached, and how far back 'last month' reaches, so added context is modest.

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?

Two short sentences, period semantics front-loaded before the per-value breakdown, with no filler. The opening fragment 'A day or month in short' is slightly awkward but does not waste space.

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 one-parameter read-only tool with an output schema, the description covers what matters: the two periods, the default, and the returned contents. Only the relationship to the sibling time-series tools (ams_now, ams_price) is left unaddressed.

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 single enum parameter is documented only by the schema's enum list and default, so the description carries real weight here: it explains what each of the two values actually yields. That is meaningful meaning added beyond the bare enum.

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 makes clear that ams_history returns a summary of a day or a month, and it names the concrete contents (today so far plus busiest hour; this month so far, busiest day, last month). There is no explicit verb and no differentiation from siblings such as ams_now, but the resource and return content are unmistakable.

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?

It tells the agent which period value to pick and states that 'day' is the default, which is useful selection guidance within the tool. It never says when to reach for ams_history rather than ams_now or the other siblings, so the usage context is only implied.

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