Skip to main content
Glama
Sign In

BLS OEWS

by com.1102tools
OverviewDiscussionsAdmin

detect_latest_year

Read-only

Report the OEWS data year this server answers from.

OEWS releases annually in spring, and this server bundles the current release. Every tool defaults to that year. When BLS publishes a newer release, a new package version bundles it.

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": "detect_latest_year"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely new context: the year is fixed per package version, is not fetched live, and changes only when a new package bundles a newer BLS release. That is exactly the kind of 'why this value is static' detail annotations cannot express.

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?

The answer is front-loaded in the first sentence, with supporting context after it. The release-cadence details are relevant but slightly padded, and the trailing 'a new package version bundles it' restates the preceding sentence's point.

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?

An output schema exists, so return-value explanation is unnecessary. The description covers staleness expectations (spring releases, bundled per version), which is the main confusion risk for a year-reporting tool. The only gap is failing to position it against get_data_status in the sibling set.

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 tool takes zero parameters, which is the baseline-4 case. There is nothing for the description to disambiguate, and it does not waste words inventing parameter guidance.

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?

States a specific verb and resource: reports the OEWS data year the server is bundled with. That is far more precise than the name alone. However, it never distinguishes itself from the sibling get_data_status, which plausibly also reports server/data state, so an agent must guess between them.

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?

The line 'Every tool defaults to that year' implies this is a metadata lookup you can call to learn the data vintage before querying wages. But there is no explicit when-to-use statement, no exclusions, and no mention of get_data_status as the alternative for broader status information.

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

All BLS OEWS toolsInspect
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