Skip to main content
Glama

BRAINIAC Global Employment Rules

Check UK working-time limits

global-employment_uk-working-time-check
Read-onlyIdempotent

Check caller-supplied shifts against UK 48-hour average, under-18 limits, 20-minute breaks, daily rest, and weekly or fortnightly rest rules. Price $0.04 USDC. POST /api/v1/global-employment/uk-working-time-check. An unpaid call returns the x402 payment terms and does not run.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "shifts": "<shifts>"
    },
    "name": "global-employment_uk-working-time-check"
  }
}

Input Schema

NameRequiredDescriptionDefault
shiftsYesshifts, array. Required.
under18Nounder18, boolean. Required.
optedOutNooptedOut, boolean. Required.
referenceWeeksNoreferenceWeeks, integer, from 1 to 52. Required.

Output Schema

NameRequiredDescriptionDefault
okNook. Boolean.
sourcesNosources. Array.
violationsNoviolations. Array.
limitationsNolimitations. Array.
averageWeeklyHoursNoaverageWeeklyHours. Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world. The description adds genuinely useful context beyond them: a $0.04 USDC price, the POST endpoint, and the behavior that an unpaid call returns payment terms rather than executing. It does not describe what a result contains or how failures surface, and output schema coverage limits the need.

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?

Tight, front-loaded: rule scope first, then pricing, endpoint, and payment behavior. Three sentences, no filler. Slight density cost from the API/pricing details embedded mid-paragraph, but every sentence conveys actionable information.

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?

For a payment-gated compliance tool with an output schema, the essentials are present: what it checks, what it costs, and what happens without payment. Missing are result interpretation cues (pass/fail shape, breach details) and whether shifts may span timezones or cross date boundaries, which matters for date-time parsing.

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

Parameters3/5

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

Schema coverage is 100%, so start/end/breakMinutes/shifts/under18/optedOut/referenceWeeks are all documented in the schema. The description adds semantic framing by naming what the rules measure (48-hour average, 20-minute breaks), but does not explain the meaning of optedOut or referenceWeeks beyond the schema. Baseline 3 given full schema coverage.

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+resource: check shifts against UK 48-hour average, under-18 limits, breaks, and rest rules. The enumerated rule set clearly distinguishes it from sibling calculators like statutory redundancy pay or US overtime. It stops short of naming which sibling to use instead when a query spans jurisdictions.

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

Usage Guidelines4/5

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

Implies usage context (UK working-time compliance checks on caller-supplied shifts) and signals an alternative path for payment: an unpaid call returns x402 terms instead of results. No explicit when-not guidance or sibling routing, but the domain scope is clear enough to select confidently.

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