Skip to main content
Glama

BRAINIAC HR Operations

Check document expiry

hr-operations_workforce-document-expiry-check

Compare supplied expiry dates with a supplied as-of date. A document is due only inside the supplied day window. No date is invented when the as-of date is missing. Price $0.04 USDC. POST /api/v1/hr-operations/workforce-document-expiry-check. Unpaid calls return 402 and do not run.

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": "hr-operations_workforce-document-expiry-check"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
asOfNo
fileNo
jsonNo
textNo
policiesNo
roleTextNo
documentsNo
employeesNo
withinDaysNo
completionsNo
employeeTextNo
requirementsNo
acknowledgementsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose real behavior: pricing ($0.04 USDC), that unpaid calls return 402 and do not run, and that no date is invented when the as-of date is missing. It still says nothing about which of the many input sources takes precedence, what the response contains, or how missing/invalid dates are handled.

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?

Short, front-loaded sentences with the core comparison stated first and the operational facts (price, endpoint, 402 behavior) trailing. The endpoint path is arguably filler, but nothing is padded or redundant.

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?

For a 14-parameter tool with nested objects, no annotations, and no output schema, the description is far too thin. An agent cannot determine which input shape to supply or what the result looks like from this text alone.

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?

Schema description coverage is 0% across 14 parameters, and the description only touches asOf, expiry dates, and the day window (withinDays). It never explains the csv/json/text/file alternatives, the documents/employees/policies/requirements/completions/acknowledgements arrays, or roleText/employeeText, leaving most parameters undocumented in both places.

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: compare supplied expiry dates against a supplied as-of date, with the day-window scoping rule. It is clear what the tool computes, though it never names a sibling or explicitly contrasts itself with the other hr-operations checks.

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 description implies the use case (finding documents due to expire within a window) and gives the rule that a document is due only inside the supplied day window. It offers no explicit when-to-use versus when-not-to-use guidance and no prerequisites, so the agent must infer the context.

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