Skip to main content
Glama

BRAINIAC HR Operations

Report personnel record completeness

hr-operations_record-completeness-report

Combine supplied records, document dates, policy acknowledgements, onboarding and offboarding items, and role duties. The report does not determine legal compliance or change access. Price $0.12 USDC. POST /api/v1/hr-operations/record-completeness-report. 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_record-completeness-report"
  }
}

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.4/5.0
Behavior4/5

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

With no annotations at all, the description still discloses non-obvious operational behavior: a $0.12 USDC price, a fixed POST endpoint, and that unpaid calls return 402 without executing. It also clarifies the operation is read-only in effect ('does not change access'). It stops short of describing the response contents or what happens when no input data is supplied.

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?

Front-loaded with the purpose, followed by scope limits, then price, endpoint, and payment failure mode. Sentences are short and free of filler; the price/endpoint/402 details are operationally necessary given no annotations, though they read as transport metadata rather than usage guidance.

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

Completeness3/5

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

Covers the operation's identity, cost, and failure mode, which is real value for an unannotated tool. But for a 14-parameter, deeply nested tool with no output schema, it omits the two things an agent most needs: how to choose among the five alternative input encodings and what the report actually contains.

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?

With 14 parameters and 0% schema description coverage, the description must carry the burden and only partially does: it maps loosely to employees, documents, policies, acknowledgements, and role duties. It says nothing about the mutually exclusive input modes (csv, json, text, file, or structured arrays), nor about asOf, withinDays, requirements[].field, or the completions array, which are the hardest parts for an agent to get right.

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 aggregation purpose: combining personnel records, document dates, policy acknowledgements, onboarding/offboarding items, and role duties into a completeness report. It is distinguishable from siblings like employee-record-validate by the multi-source 'combine' scope and the explicit disclaimer that it does not determine legal compliance. The verb 'Combine' is slightly generic, but the enumerated inputs make the resource concrete.

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 'does not determine legal compliance or change access' functions as a when-not hint and implicitly routes compliance judgments elsewhere. However, there is no explicit instruction on when to choose this over employee-record-validate or the individual checklist tools, and no guidance on which input combination is required given that all 14 parameters are optional.

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