Skip to main content
Glama

BRAINIAC HR Operations

Extract employee documents

hr-operations_employee-document-extract

Read employee records and labeled document lines supplied by the caller. Dates, roles, and document types are returned as supplied. Document numbers are masked. Price $0.04 USDC. POST /api/v1/hr-operations/employee-document-extract. 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-document-extract"
  }
}

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.6/5.0
Behavior3/5

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

With no annotations, the description must carry the full behavioral burden, and it does disclose several useful traits: pass-through semantics for dates/roles/document types, masking of document numbers, cost ($0.04 USDC), the POST endpoint, and that unpaid calls return 402 without executing. It omits whether the operation mutates state, whether it is idempotent, and how invalid or oversized inputs fail.

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 text is short and begins with the operation, but it devotes half its length to pricing and transport boilerplate (price, endpoint path, 402 behavior) while omitting the substantive input semantics that actually need explanation. Compact, but the allocation of words is misaligned with what an agent needs.

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, no output schema, and no schema descriptions, the description is far too thin. It covers billing and masking but not what the tool computes, what the output contains, or how the many input collections relate to each other.

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 including nested objects (employees, documents, policies, completions, requirements, acknowledgements, file). The description only vaguely gestures at 'employee records and labeled document lines' and says nothing about asOf, withinDays, policies, completions, requirements, acknowledgements, or the csv/json/text/file input variants, leaving the bulk of the schema unexplained.

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 description says it reads employee records and labeled document lines supplied by the caller, which identifies the resource and input mode, but never states what 'extract' produces (a validation result? a parsed table? a rule evaluation?). Nothing distinguishes it from siblings like employee-record-validate or record-completeness-report, so an agent cannot disambiguate from purpose alone.

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 when-to-use guidance, no exclusions, and no mention of alternatives among the seven sibling HR operations tools. The only conditional content is the payment gate ('unpaid calls return 402'), which is a billing rule, not usage guidance.

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