# NoiseMeters MCP

> NoiseMeters API connects your AI client directly to environmental sound data streams. It lets you read real-time decibel levels, audit historical noise recordings, and manage instrument catalogs for compliance checks. Use it when you need to track acoustic changes or verify sensor health without a GUI.

## Overview
- **Category:** scientific-research
- **Price:** Free
- **Tags:** noise-monitoring, decibel-tracking, environmental-data, acoustic-analysis, sensor-data

## Description

Yo, listen up. The **NoiseMeters API** gives your AI client direct, unfiltered access to environmental sound data streams. Forget clicking through dashboards; this server lets you run complex acoustic audits straight from your agent's prompt. You use it when you gotta check decibel levels or verify sensor health without touching a graphical user interface.

To start any work, first you need to know if the system's up for grabs. Your agent uses `check_api_status` to confirm the entire NoiseMeters service is fully operational and ready to accept calls. This quick check tells you whether or not it's safe to run a data pull.

When you need to inventory your gear, you gotta know what sensors you're running. The `list_noise_instruments` tool spits out a complete list of every monitoring device registered under your account ID. If you then want the specifics on one piece of hardware—like checking its technical specs or metadata—your agent can pull detailed info for that specific instrument ID.

Need to know what's happening right now? You use `get_live_noise_data`. It grabs the most recent, current noise level in decibels (dB) from a single monitoring device. That’s your instant read on the ambient sound at a specific location.

But let's be real; live data only tells half the story. For compliance or deep analysis, you need history. You use `get_noise_measurements` to fetch time-series data. This lets your agent pull historical noise readings for an instrument across a defined date range, building out a full audit trail of acoustic changes over time.

When you put all this together—checking the status, listing the inventory, grabbing live reads, and pulling years of measurements—you can build robust compliance checks. You don't need to manually cross-reference sheets or wait for reports. Your agent handles it all, giving you verified data points that prove whether industrial limits were breached or if urban sound patterns shifted during a specific timeframe. It’s pure, actionable acoustic intelligence delivered right where your client needs it.

## Tools

### check_api_status
Verifies if the entire NoiseMeters service is operational and ready for data calls.

### get_live_noise_data
Retrieves the most recent, current noise level (dB) reading from a specific instrument ID.

### get_noise_measurements
Fetches time-series data showing historical noise readings for an instrument over a specified date range.

### list_noise_instruments
Returns a complete list of every monitoring device registered under the account ID.

## Prompt Examples

**Prompt:** 
```
Get live noise data for instrument 'INS-12345' using NoiseMeters.
```

**Response:** 
```
I've retrieved the live noise data for instrument INS-12345! The current level is identified as 65.2 dB. Would you like the historical measurement metadata or the location details for this site?
```

**Prompt:** 
```
List all my noise monitoring instruments.
```

**Response:** 
```
I've retrieved your instrument catalog from NoiseMeters! You have 3 active devices, including 'Factory-South' and 'Site-Alpha'. I can provide the real-time decibel metadata for any of these instruments.
```

**Prompt:** 
```
Show noise measurements for 'INS-67890' starting from '2024-05-01'.
```

**Response:** 
```
I've identified the measurements for that instrument! There were 24 entries recorded since May 1st. I can assist you with an audit of the peak sound intensity and duration markers if you'd like.
```

## Capabilities

### Check System Status
Verifies if the NoiseMeters API is online and ready to accept requests.

### Get Live Decibel Reading
Pulls the single most recent, real-time noise level (in dB) for a specific monitoring device.

### Retrieve Historical Measurements
Fetches a time series of past noise readings for an instrument over a defined period.

### List All Instruments
Returns a complete catalog list of every registered monitoring device in your account.

### Check Instrument Metadata
Retrieves detailed technical data and specifications for any specific instrument ID.

## Use Cases

### Checking Compliance After Construction
A construction site manager needs to check if noise levels exceeded local limits last Tuesday. They ask their agent: 'What were the decibel readings for Site-West between 2pm and 4pm on May 15th?' The agent uses `get_noise_measurements` with the correct date range, pulling a structured log that proves compliance or flags violations.

### Verifying Equipment Status
An operations lead needs to know if all monitoring equipment is online right now. They ask their agent: 'List all active noise monitors.' The agent uses `list_noise_instruments` and then runs `get_live_noise_data` for each device, providing a single status report on every sensor.

### Quick Field Audit
A safety officer arrives at a site and needs an immediate reading. They ask: 'What's the current dB level at Unit 4?' The agent uses `get_live_noise_data` with the unit ID, providing a single number immediately, letting the officer make a call without delay.

### Debugging Data Gaps
An engineer notices some data looks suspiciously sparse. They first run `check_api_status` to rule out system failure. If that passes, they use `list_noise_instruments` to confirm the sensor ID is correct before trying `get_noise_measurements` again.

## Benefits

- Real-Time Auditing: Use `get_live_noise_data` to pull the immediate decibel reading for any sensor. This cuts out the need to log into a dashboard just to check if things are running hot right now.
- Compliance History: The `get_noise_measurements` tool pulls time-series data, letting you quickly audit months of readings. You get the full paper trail needed for regulatory reports.
- Inventory Control: `list_noise_instruments` gives a clean roster of every device ID in your account. This is critical for making sure you're tracking all required monitoring points.
- Reliability Check: Before running any big audit, run `check_api_status`. It tells you if the whole system is up or if you're going to hit an error wall. Saves time and headaches.
- Targeted Data Pulls: You don't get dumped a giant data dump. The tools let your agent target specific instruments and date ranges, keeping the output clean and actionable.

## How It Works

The bottom line is: you tell your agent what data point you need, and it executes the API call using the right tool to pull the numbers.

1. Subscribe to the NoiseMeters server and provide your API Key.
2. Your AI client invokes a tool (e.g., `get_live_noise_data`), passing the required instrument ID.
3. The agent receives the structured data—either real-time measurements or historical logs.

## Frequently Asked Questions

**How do I check if NoiseMeters API is working?**
You use `check_api_status`. This tool simply confirms the service is operational before you run any expensive or critical measurements. It's your system health check.

**What information does list_noise_instruments provide?**
`list_noise_instruments` provides a comprehensive catalog of every monitoring sensor ID registered to your account. You use this to ensure you don't miss any required measurement points.

**Can I get noise data for multiple sites at once with NoiseMeters API?**
No, not in one call. First, use `list_noise_instruments` to get all IDs. Then, you run `get_live_noise_data` individually for each ID you need a reading from.

**What if my historical data is incomplete? How does get_noise_measurements help?**
`get_noise_measurements` retrieves time-series logs. If the data looks sparse, you should run `check_api_status` first to rule out a system outage.

**What units does the `get_live_noise_data` tool return?**
It returns the current noise level exclusively in decibels (dB). This single measurement gives your agent the immediate, real-time acoustic intensity of the site.

**How do I secure my connection when using NoiseMeters API?**
You must use a unique API Key during setup. The key authorizes your AI client to access all measurement endpoints and protects your environmental data from unauthorized reads.

**What kind of metadata does `list_noise_instruments` provide?**
It provides more than just device names; the tool returns unique IDs, location coordinates, and status flags for every registered instrument. This helps your agent map data sources precisely.

**Are there rate limits when calling `get_noise_measurements`?**
Yes, rapid or excessive calls might hit a usage limit. Always check the service documentation for current request quotas to prevent any interruption to your acoustic research workflow.

**How do I find my NoiseMeters API Key?**
Log in to your [**NoiseMeters dashboard**](https://api.noisemeters.com/), and you will find your API Key under your account or integrations section. Copy and paste it below.

**Does it support real-time sound levels?**
Yes. The `get_live_noise_data` tool provides the most recent decibel measurement received from the specified instrument ID.

**Can the agent list my monitoring instruments?**
Yes. The `list_noise_instruments` tool retrieves all noise monitoring devices registered in your account with their unique identifiers and names.