decibel-shield

Look up how loud a common sound is

lookup_sound_level

Read-onlyIdempotent

Answers "how loud is a hair dryer", "how many decibels is a chainsaw", "is 85 decibels loud", "how loud is 80 decibels". Decibel level and hearing-risk guidance for everyday sounds (whisper, conversation, traffic, lawn mower, concert, jet engine...), every figure sourced to CDC/NIOSH/NIDCD/ASHA published tables. Input is a sound name; if you already have a dB number and want safe listening time, use safe_exposure_time.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`sound`	Yes	Sound to look up, e.g. "lawn mower" or "subway"

Output Schema

TableJSON Schema

Name	Required	Description	Default
`matches`	Yes
`attribution`	No

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already indicate readOnlyHint, idempotentHint, and destructiveHint. The description adds value by stating the tool provides decibel level and hearing-risk guidance, and that figures are sourced from authoritative organizations (CDC, NIOSH, NIDCD, ASHA), offering behavioral context beyond what annotations provide.

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?

The description is concise, using a short paragraph that front-loads examples, states the tool's output, and provides an alternative. Every sentence serves a purpose with no waste.

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

Completeness5/5

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

Given one fully-documented parameter, existing annotations, an output schema, and sibling tools that provide context, the description is complete. It covers purpose, usage, and alternative, making it sufficient for agent understanding.

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

Parameters3/5

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

Schema coverage is 100% with a description for the 'sound' parameter. The description repeats that input is a sound name but adds no new semantic meaning beyond the schema. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states that the tool answers questions about how loud common sounds are, providing decibel levels and hearing-risk guidance. It gives concrete examples like 'hair dryer' and 'chainsaw', and distinguishes itself from sibling tools by mentioning an alternative for dB numbers.

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

Usage Guidelines5/5

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

Explicitly tells when to use this tool (when you have a sound name and want decibel information) and when to use the alternative (safe_exposure_time for dB numbers wanting safe listening time). This provides clear guidance on tool selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All decibel-shield tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose: address-level noise, city-level estimated (world), city-level measured (Europe), US city exposure, neighborhood ranking, ordinance info, sound level lookup, safe exposure time, and app information. Overlaps are minimal and well-documented in descriptions.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (get_, list_, lookup_, safe_). Naming conventions are uniform, using lowercase with underscores, making it easy to predict tool names from the domain.

Tool Count5/5

With 10 tools, the server is well-scoped for its purpose of providing noise information. Each tool covers a specific aspect of the domain without redundancy, and the number is within the ideal 3-15 range.

Completeness4/5

The tool set covers address, neighborhood, US city, European city, and world city noise, plus sound levels, safe exposure, and some ordinances. Minor gaps include limited ordinance coverage (only 8 US cities) and lack of noise data for non-European/non-US regions, but core queries are addressed.

Resources

Need Help?