Skip to main content
Glama

BRAINIAC HR Operations

Validate employee records

hr-operations_employee-record-validate

Compare employee records with the required fields supplied by the caller, and report an end date that falls before the start date. No legal requirement is added. Price $0.04 USDC. POST /api/v1/hr-operations/employee-record-validate. 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_employee-record-validate"
  }
}

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

C2.2/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It does disclose genuinely useful traits — the $0.04 USDC price, that unpaid calls return 402 and do not execute, and that no legal requirement is asserted — which is real value. However, for a 14-parameter nested-object tool it says nothing about whether the call is a pure read, what the response contains, how many findings are returned, or what happens with partial/overlapping inputs.

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?

Four short sentences, each carrying distinct information (purpose, scope disclaimer, price, endpoint, payment failure mode). Front-loaded with the operation. The URL path largely restates the tool name, but overall there is little waste.

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

Completeness1/5

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

The tool is complex: 14 parameters, nested objects, multiple alternative input encodings, no output schema, and no annotations. Against that complexity the description covers essentially none of the input contract or result shape, leaving an agent unable to construct a correct call from the description alone.

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

Parameters1/5

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

Schema description coverage is 0% across 14 parameters, including nested employees, documents, policies, requirements, completions, and acknowledgements. The description only obliquely gestures at two of them ('employee records', 'required fields supplied by the caller') and never explains the csv/json/text/file alternative inputs, asOf, withinDays, employeeText, or roleText. It fails to compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first clause gives a verb+resource ('Compare employee records with the required fields supplied by the caller'), which is specific enough to understand the operation. But the following clause ('report an end date that falls before the start date') is garbled and reads as if the tool returns a date rather than flags an invalid date range. It never differentiates itself from close siblings such as record-completeness-report or employee-policy-acknowledgement-check.

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

Usage Guidelines2/5

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

There is no guidance on when to choose this validator versus the completeness report, document expiry check, or policy acknowledgement check. Nothing states prerequisites for the caller-supplied requirements or when validation is inappropriate. Only pricing and transport details are given.

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