Skip to main content
Glama

get_employment_cost_index

Read-only

BLS Employment Cost Index year-over-year change for total compensation, wages, and benefits. Use when modeling labor cost inflation, contract escalation, and margin pressure in operating plans. Source: BLS ECI. $0.10 standard. Cryptographically attested with a post-quantum signed settlement receipt. Verify at trust.stratalize.com/verify.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered by structured data. The description adds the data source (BLS ECI), the price ($0.10 standard), and an attestation/verification path. It does not state data freshness, publication lag, or geographic or industry coverage, which would matter for a macroeconomic benchmark.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first two sentences are tight and front-loaded with purpose and use case. The final sentence about post-quantum signed settlement receipts and verification at trust.stratalize.com is promotional filler that does not help an agent decide or invoke.

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?

For a parameterless, read-only benchmark with no output schema, the description gives enough to select and call it correctly. It is only slightly incomplete in not hinting at return granularity (e.g., a single national series versus breakdowns).

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?

With zero parameters there is nothing for the description to disambiguate, and the baseline for a parameterless tool is 4. The description correctly implies the tool takes no filters and returns a fixed series.

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?

The description names a specific verb and resource: 'BLS Employment Cost Index year-over-year change for total compensation, wages, and benefits,' so an agent knows exactly what data this returns. It does not distinguish itself from nearby siblings such as get_bls_sector_employment or get_bls_inflation_components, so it falls short of a 5.

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 states concrete use cases: 'modeling labor cost inflation, contract escalation, and margin pressure in operating plans.' That is clear positive guidance, but it names no alternatives and no when-not-to-use conditions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources