BatterySnap

List brands

brands

Read-onlyIdempotent

Return the mobile devices brands for which we have battery statistics, along with the number of distinct models, the number of devices recorded per brand, and the largest single-model device count within the brand (max_devices_per_model). Each entry also includes a url to the public BatterySnap web page for the brand (e.g. https://www.battery-snap.com/brands/samsung). Pass min_device_count / max_device_count and min_model_count / max_model_count to filter brands by recorded-device and distinct-model counts. Pass fields to keep only specific attributes in each entry. The full list is long: pass limit (and offset to page) unless you really need every brand, and prefer search when resolving one brand by name.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Return at most this many entries. Omit for no cap — but the unbounded list can be very large, so prefer a limit.
`fields`	No	Optional whitelist of attribute names to keep in each returned entry, used to shrink the response. When omitted or empty, all attributes documented in the output schema are returned. Unknown names are silently ignored.
`offset`	No	Skip this many entries before returning results — use with `limit` to page through a long list. Defaults to 0.
`max_model_count`	No	Drop brands with more than this many distinct models. Omit for no upper bound.
`min_model_count`	No	Drop brands with fewer than this many distinct models. Defaults to 0 (keep all).
`max_device_count`	No	Drop entries with more than this many recorded devices. Use to skip very common entries. Omit for no upper bound.
`min_device_count`	No	Drop entries with fewer than this many recorded devices. Defaults to 1 (keep all).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 16, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, openWorldHint=false), so the bar is lower. The description adds useful behavioral context the annotations do not: the unbounded list can be very large, and `fields` names that are unknown are silently ignored.

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?

Return shape is front-loaded, followed by filtering, field projection, and paging advice; each sentence has a job. It is somewhat wordy in restating parameter behavior the schema already carries, which keeps it below a 5.

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?

With an output schema present, the description need not detail return values, and the annotations carry the safety profile; the remaining gaps an agent would care about (list size, paging, single-brand routing) are all covered.

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 description coverage is 100%, so the schema already documents all seven parameters including defaults and bounds. The description restates the filter pairs, `fields`, and `limit`/`offset` paging but adds no syntax or semantics beyond what the schema provides, so the baseline 3 applies.

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?

States a specific verb and resource (return device brands with battery statistics) and enumerates the returned aggregates (model count, device count, max_devices_per_model, url). It also carves out its scope against the `search` sibling, so an agent can tell what this tool is for without opening the schema.

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

Usage Guidelines4/5

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

Gives concrete operating guidance: prefer `search` when resolving a single brand by name, and pass `limit` unless the full list is genuinely needed. It stops short of a full when-not statement (e.g. when to prefer model- or device-level siblings), but the alternative-tool routing is explicit.

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

All BatterySnap tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?