Skip to main content
Glama

BRAINIAC HR Operations

Check policy acknowledgements

hr-operations_employee-policy-acknowledgement-check

Match supplied acknowledgements to supplied policies by policy id. An acknowledgement dated before the policy date is stale. This is not a compliance determination. Price $0.04 USDC. POST /api/v1/hr-operations/employee-policy-acknowledgement-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_employee-policy-acknowledgement-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 does contribute real behavioral facts: price ($0.04 USDC), the endpoint, and that unpaid calls return 402 without running — all of which matter to an agent. However, it says nothing about what the matching produces, how missing employees or documents are handled, or the response shape, leaving significant behavioral gaps for a 14-parameter tool.

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 description is short and front-loads the core matching behavior before the caveat and payment mechanics. The literal POST path restates the tool name and is largely wasted space, keeping it from a 5.

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 tool with 14 parameters, nested objects, no output schema, and no annotations, the description is far too thin. It omits the input-mode selection, the date/filter parameters, and any hint of what a result contains, so an agent lacks what it needs to construct a correct call.

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, so the description must compensate and largely does not. It explains the acknowledgements-to-policies link by policy id, but never covers the multiple input modes (csv, json, text, file, employeeText, roleText), asOf, withinDays, or the employees/documents/requirements/completions arrays — an agent cannot tell which inputs are required or mutually exclusive.

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 states a specific verb and resource: match supplied acknowledgements to supplied policies by policy id, plus the staleness rule. It also carves out scope with 'This is not a compliance determination'. It does not explicitly distinguish itself from siblings such as record-completeness-report, 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 Guidelines3/5

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

There is a single negative scope hint ('not a compliance determination') that tells the agent what this tool is not, but no positive guidance on when to prefer it over the expiry-check or completeness-report siblings, and no prerequisites are stated. Usage is only implied.

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