Skip to main content
Glama

BRAINIAC HR Operations

Compare a role description

hr-operations_job-role-description-compare

Compare Duty lines in a role description with Duty lines supplied for an employee. Unlabeled prose is not a duty. The comparison is not an employment decision. Price $0.04 USDC. POST /api/v1/hr-operations/job-role-description-compare. 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_job-role-description-compare"
  }
}

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

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

With no annotations supplied, the description does carry real behavioral load and delivers some of it: price ($0.04 USDC), the POST endpoint, and the failure mode that unpaid calls return 402 and do not run. It says nothing about what a successful response contains, whether the tool is read-only or persists anything, or how ambiguous duty matches are resolved, which matters for a 14-parameter analysis 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?

Sentences are terse and the core comparison statement is front-loaded, followed by the scoping rule, caveat, and operational facts. No filler, though the jump from domain semantics to price/endpoint metadata is a bit abrupt.

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 optional parameters, deeply nested objects, no annotations, no output schema, and zero schema descriptions, this description covers only the high-level intent and billing behavior. An agent could not reliably construct a correct call from it, particularly the relationships among employees, requirements, completions, and policies.

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 hints at roleText and employeeText via 'role description' and 'Duty lines supplied for an employee', but csv, json, file, text, asOf, withinDays, policies, documents, employees, completions, requirements, and acknowledgements are entirely undocumented and their roles are unguessable.

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 (Compare) and a specific resource (Duty lines in a role description vs. Duty lines supplied for an employee), and adds the disambiguating rule that unlabeled prose does not count as a duty. It does not, however, pin down how the comparison is expressed or which input fields carry each side, so the mechanics remain partly opaque.

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 statement of when to use this tool rather than the sibling checks (policy-acknowledgement-check, record-validate, etc.), no prerequisites, and no exclusions. The line 'The comparison is not an employment decision' is a legal caveat about interpretation, not usage guidance that helps an agent choose.

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