Skip to main content
Glama

AlpineDataWorks Intelligence Server

by com.alpinedataworks

Library Access Index

adw.adw_511
Read-only

Returns a 0-100 public library access score for any of 3,222 US counties (per-capita branch density, service hours, and service-capacity measures, normalized to the national distribution) with score, national_percentile, driver attributions, confidence, and methodology_version. Call when the user asks about library access, civic or educational infrastructure, or digital-equity gaps, or when timing grant targeting, levy proposals, or public-sector market prioritization. Updates: on source cadence.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoOptional: return a daily HISTORY series of the last N days (up to 5 years of real archived data) instead of the current snapshot. History requires Gold tier; without it, the current snapshot is returned.

TDQS

A3.5/5.0
Behavior2/5

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

The description claims the tool works for 'any of 3,222 US counties' but the input schema has no parameter to specify a county. This is a significant behavioral inconsistency that leaves the agent unable to select the target county, and the description does not clarify how the county is determined.

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 and front-loaded, with the main purpose in the first sentence, usage guidance in the second, and an update cadence note in the third. Every sentence provides useful information without fluff.

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

Completeness2/5

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

The tool is described as returning per-county scores, yet the schema only includes an optional 'days' parameter with no county selector. No output schema exists, and the description fails to explain how to obtain a score for a specific county, making the tool practically incomplete.

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

Parameters2/5

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

The schema fully documents the optional 'days' parameter, but the description never mentions it and instead implies a non-existent county selector. This adds confusion rather than meaning to the actual parameter.

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 the tool returns a 0-100 public library access score for US counties, naming specific measures and output fields. This is a specific verb and resource that distinguishes it from sibling tools.

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?

It provides explicit use cases such as library access, civic/educational infrastructure, digital-equity gaps, and grant timing, giving clear context for when to call. However, it does not mention exclusions or name alternative tools.

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

All AlpineDataWorks Intelligence Server toolsInspect
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

B3.3/5.0
Disambiguation1/5

With 318 tools named adw.adw_###, agents cannot tell them apart without reading full descriptions. Multiple tools cover the same domain (e.g., at least three USD strength scores: adw_055, adw_250, adw_580; four supply-chain stress scores: adw_009, adw_019, adw_020, adw_547), making misselection highly likely.

Naming Consistency3/5

The vast majority follow a consistent numeric ID pattern (adw.adw_###), but a small set breaks this with descriptive snake_case names (adw.catalog, adw.sample, adw.county_cancer, etc.). The numeric IDs are predictable but convey no semantic meaning, mixing with the few named tools and creating moderate inconsistency.

Tool Count1/5

318 tools is far beyond any reasonable scope for an intelligence server; even the largest sophisticated APIs rarely exceed 50. This extreme count suggests poor curation and will overwhelm agents with choice, making efficient tool selection impractical.

Completeness3/5

The server covers an extremely broad range of domains (crypto, macro, supply chain, healthcare, climate, county demographics), and includes discovery tools like adw.catalog and adw.sample. However, the surface is redundant and not systematically complete—many overlapping indices exist while other potentially valuable operations (e.g., raw data export, historical trend queries) are missing, leaving moderate gaps.

Resources