Skip to main content
Glama

Afriref: cited government reference data

count_working_days

Read-onlyIdempotent

PAID ($0.002). Working days in a date range for a country: weekends (Egypt's Fri–Sat handled) and statutory public holidays applied, with the holidays hit by name and the next working day after the range. Range max 366 days. Pass api_key if you have one (instant card checkout at /pricing); otherwise the response explains how to pay via x402. The evaluation country is free to try (see list_series). Optional receipt (boolean, default false): on a paid success, include an Ed25519 answer receipt at no extra USDC. An answer receipt is not a series certified extract (GET /v1/certified/{country}/{series} is $0.10 and is not an MCP tool) and is not legal advice. Verify with verify_answer_receipt against /certified/public-key.

Input Schema

NameRequiredDescriptionDefault
toYesRange end, YYYY-MM-DD, inclusive
fromYesRange start, YYYY-MM-DD, inclusive
api_keyNoAPI key
countryYesISO country code
receiptNoDefault false. When true, a paid success includes an Ed25519 answer receipt (kind answer_receipt) at no extra USDC. Unpaid 402 and free refusals do not include one. Not a series certified extract (GET /v1/certified/{country}/{series} at $0.10; that SKU is not an MCP tool).
subdivisionNoOptional ISO 3166-2 region code (e.g. 'DE-BY') to apply that region's statutory holidays on top of the national calendar. Regions are listed under `subdivisions` by get_public_holidays. Unknown code is refused free with the list.

Output Schema

NameRequiredDescriptionDefault
basisNo
errorNoPresent on a free refusal or error; no charge
statusNoAnswer status, e.g. computed or an honest no-answer status
countryNo
receiptNoEd25519 answer receipt when receipt=true on a paid success
questionNo
no_chargeNo
price_usdNo
disclaimerNo
how_to_payNo
provenanceNoCited official sources behind the answer
bind_seriesNo
explanationNo
label_basisNoInputs and the rule ids that produced the two labels
x_next_bindNo
http_endpointNo
coverage_labelNoHow much of the question is covered: ready = complete; partial = held with a disclosed limitation or default; gap = no number served. Rules at /label-rules
confidence_labelNoEvidence verdict derived from source type, verification age and the stale flag (answers: the weakest series read). Rules at /label-rules
payment_requiredNotrue when the call needs payment; how_to_pay explains x402 or card

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedOutput schema / properties / label_basis / properties / source_type / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / label_basis / properties / source_type / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / label_basis / properties / verification_age_days / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / label_basis / properties / verification_age_days / type
      Added value: +[
      +  "number",
      +  "null"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / receipt / description
      Previous value: -"Default false. When true, a paid success includes an Ed25519 answer receipt (kind answer_receipt) at no extra USDC. Unpaid 402 and free refusals do not include one. Not a series certified extract (GET /v1/certified/{country}/{series} at $0.25; that SKU is not an MCP tool)."New value: +"Default false. When true, a paid success includes an Ed25519 answer receipt (kind answer_receipt) at no extra USDC. Unpaid 402 and free refusals do not include one. Not a series certified extract (GET /v1/certified/{country}/{series} at $0.10; that SKU is not an MCP tool)."
  3. Changed3 schema fields changed
    • addedOutput schema / properties / confidence_label
      Added value: +{
      +  "description": "Evidence verdict derived from source type, verification age and the stale flag (answers: the weakest series read). Rules at /label-rules",
      +  "enum": [
      +    "high",
      +    "medium",
      +    "low"
      +  ],
      +  "type": "string"
      +}
    • addedOutput schema / properties / coverage_label
      Added value: +{
      +  "description": "How much of the question is covered: ready = complete; partial = held with a disclosed limitation or default; gap = no number served. Rules at /label-rules",
      +  "enum": [
      +    "ready",
      +    "partial",
      +    "gap"
      +  ],
      +  "type": "string"
      +}
    • addedOutput schema / properties / label_basis
      Added value: +{
      +  "additionalProperties": {},
      +  "description": "Inputs and the rule ids that produced the two labels",
      +  "properties": {
      +    "confidence_reasons": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "coverage_reasons": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "inputs": {
      +      "items": {},
      +      "type": "array"
      +    },
      +    "rules": {
      +      "type": "string"
      +    },
      +    "rules_version": {
      +      "type": "string"
      +    },
      +    "source_type": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    },
      +    "stale": {
      +      "type": "boolean"
      +    },
      +    "verification_age_days": {
      +      "anyOf": [
      +        {
      +          "type": "number"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    }
      +  },
      +  "type": "object"
      +}
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": {},
      +  "description": "Working-day count over a range with holidays hit",
      +  "properties": {
      +    "basis": {},
      +    "bind_series": {},
      +    "country": {
      +      "type": "string"
      +    },
      +    "disclaimer": {},
      +    "error": {
      +      "description": "Present on a free refusal or error; no charge"
      +    },
      +    "explanation": {},
      +    "how_to_pay": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "http_endpoint": {
      +      "type": "string"
      +    },
      +    "no_charge": {
      +      "type": "boolean"
      +    },
      +    "payment_required": {
      +      "description": "true when the call needs payment; how_to_pay explains x402 or card",
      +      "type": "boolean"
      +    },
      +    "price_usd": {
      +      "type": "number"
      +    },
      +    "provenance": {
      +      "description": "Cited official sources behind the answer"
      +    },
      +    "question": {},
      +    "receipt": {
      +      "description": "Ed25519 answer receipt when receipt=true on a paid success"
      +    },
      +    "status": {
      +      "description": "Answer status, e.g. computed or an honest no-answer status",
      +      "type": "string"
      +    },
      +    "x_next_bind": {}
      +  },
      +  "type": "object"
      +}
  5. Changed1 schema field changed
    • addedInput schema / properties / receipt
      Added value: +{
      +  "default": false,
      +  "description": "Default false. When true, a paid success includes an Ed25519 answer receipt (kind answer_receipt) at no extra USDC. Unpaid 402 and free refusals do not include one. Not a series certified extract (GET /v1/certified/{country}/{series} at $0.25; that SKU is not an MCP tool).",
      +  "type": "boolean"
      +}
  6. Changed1 schema field changed
    • addedInput schema / properties / subdivision
      Added value: +{
      +  "description": "Optional ISO 3166-2 region code (e.g. 'DE-BY') to apply that region's statutory holidays on top of the national calendar. Regions are listed under `subdivisions` by get_public_holidays. Unknown code is refused free with the list.",
      +  "type": "string"
      +}
  7. Changed1 schema field changed
    • changedInput schema / properties / country / enum
      Previous value: -[
      -  "ao",
      -  "bf",
      -  "bj",
      -  "bw",
      -  "cf",
      -  "cg",
      -  "ci",
      -  "cm",
      -  "dz",
      -  "eg",
      -  "et",
      -  "ga",
      -  "gh",
      -  "gq",
      -  "ke",
      -  "ma",
      -  "ml",
      -  "mu",
      -  "mz",
      -  "na",
      -  "ne",
      -  "ng",
      -  "rw",
      -  "sn",
      -  "td",
      -  "tg",
      -  "tn",
      -  "tz",
      -  "ug",
      -  "zm"
      -]New value: +[
      +  "ao",
      +  "bf",
      +  "bj",
      +  "bw",
      +  "cd",
      +  "cf",
      +  "cg",
      +  "ci",
      +  "cm",
      +  "dz",
      +  "eg",
      +  "et",
      +  "ga",
      +  "gh",
      +  "gq",
      +  "ke",
      +  "ls",
      +  "ma",
      +  "ml",
      +  "mu",
      +  "mz",
      +  "na",
      +  "ne",
      +  "ng",
      +  "rw",
      +  "sn",
      +  "sz",
      +  "td",
      +  "tg",
      +  "tn",
      +  "tz",
      +  "ug",
      +  "za",
      +  "zm"
      +]
  8. Changed1 schema field changed
    • changedInput schema / properties / country / enum
      Previous value: -[
      -  "ao",
      -  "bf",
      -  "bj",
      -  "bw",
      -  "cf",
      -  "cg",
      -  "ci",
      -  "cm",
      -  "dz",
      -  "eg",
      -  "et",
      -  "ga",
      -  "gh",
      -  "gq",
      -  "ke",
      -  "ma",
      -  "ml",
      -  "mu",
      -  "mz",
      -  "na",
      -  "ne",
      -  "ng",
      -  "rw",
      -  "sn",
      -  "td",
      -  "tg",
      -  "tz",
      -  "ug",
      -  "zm"
      -]New value: +[
      +  "ao",
      +  "bf",
      +  "bj",
      +  "bw",
      +  "cf",
      +  "cg",
      +  "ci",
      +  "cm",
      +  "dz",
      +  "eg",
      +  "et",
      +  "ga",
      +  "gh",
      +  "gq",
      +  "ke",
      +  "ma",
      +  "ml",
      +  "mu",
      +  "mz",
      +  "na",
      +  "ne",
      +  "ng",
      +  "rw",
      +  "sn",
      +  "td",
      +  "tg",
      +  "tn",
      +  "tz",
      +  "ug",
      +  "zm"
      +]
  9. Changed1 schema field changed
    • changedInput schema / properties / country / enum
      Previous value: -[
      -  "bf",
      -  "bj",
      -  "bw",
      -  "cf",
      -  "cg",
      -  "ci",
      -  "cm",
      -  "eg",
      -  "et",
      -  "ga",
      -  "gh",
      -  "gq",
      -  "ke",
      -  "ma",
      -  "ml",
      -  "na",
      -  "ne",
      -  "ng",
      -  "rw",
      -  "sn",
      -  "td",
      -  "tg",
      -  "tz",
      -  "ug",
      -  "zm"
      -]New value: +[
      +  "ao",
      +  "bf",
      +  "bj",
      +  "bw",
      +  "cf",
      +  "cg",
      +  "ci",
      +  "cm",
      +  "dz",
      +  "eg",
      +  "et",
      +  "ga",
      +  "gh",
      +  "gq",
      +  "ke",
      +  "ma",
      +  "ml",
      +  "mu",
      +  "mz",
      +  "na",
      +  "ne",
      +  "ng",
      +  "rw",
      +  "sn",
      +  "td",
      +  "tg",
      +  "tz",
      +  "ug",
      +  "zm"
      +]
  10. Changed1 schema field changed
    • changedInput schema / properties / country / enum
      Previous value: -[
      -  "bf",
      -  "bj",
      -  "cf",
      -  "cg",
      -  "ci",
      -  "cm",
      -  "eg",
      -  "et",
      -  "ga",
      -  "gh",
      -  "gq",
      -  "ke",
      -  "ma",
      -  "ml",
      -  "ne",
      -  "ng",
      -  "rw",
      -  "sn",
      -  "td",
      -  "tg",
      -  "tz",
      -  "ug"
      -]New value: +[
      +  "bf",
      +  "bj",
      +  "bw",
      +  "cf",
      +  "cg",
      +  "ci",
      +  "cm",
      +  "eg",
      +  "et",
      +  "ga",
      +  "gh",
      +  "gq",
      +  "ke",
      +  "ma",
      +  "ml",
      +  "na",
      +  "ne",
      +  "ng",
      +  "rw",
      +  "sn",
      +  "td",
      +  "tg",
      +  "tz",
      +  "ug",
      +  "zm"
      +]
  11. Changed1 schema field changed
    • changedInput schema / properties / country / enum
      Previous value: -[
      -  "bj",
      -  "ci",
      -  "eg",
      -  "et",
      -  "gh",
      -  "ke",
      -  "ma",
      -  "ne",
      -  "ng",
      -  "rw",
      -  "sn",
      -  "tz",
      -  "ug"
      -]New value: +[
      +  "bf",
      +  "bj",
      +  "cf",
      +  "cg",
      +  "ci",
      +  "cm",
      +  "eg",
      +  "et",
      +  "ga",
      +  "gh",
      +  "gq",
      +  "ke",
      +  "ma",
      +  "ml",
      +  "ne",
      +  "ng",
      +  "rw",
      +  "sn",
      +  "td",
      +  "tg",
      +  "tz",
      +  "ug"
      +]
  12. Changed1 schema field changed
    • changedInput schema / properties / country / enum
      Previous value: -[
      -  "ci",
      -  "eg",
      -  "et",
      -  "gh",
      -  "ke",
      -  "ma",
      -  "ng",
      -  "rw",
      -  "sn",
      -  "tz",
      -  "ug"
      -]New value: +[
      +  "bj",
      +  "ci",
      +  "eg",
      +  "et",
      +  "gh",
      +  "ke",
      +  "ma",
      +  "ne",
      +  "ng",
      +  "rw",
      +  "sn",
      +  "tz",
      +  "ug"
      +]
  13. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already cover safety (read-only, idempotent, non-destructive), yet the description adds substantial behavior: the $0.002 price, api_key vs x402 payment paths, the 366-day range limit, the free evaluation country, and precisely what the receipt flag does and does not yield. It also warns the output is not legal advice.

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 core purpose is buried after a parenthetical price tag, and the text is a dense run-on packed with payment and legal caveats that crowd the operational facts. Everything is arguably relevant, but the structure is cluttered rather than front-loaded and clean.

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

Completeness4/5

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

An output schema exists, so return values need not be described, and the description covers pricing, payment fallbacks, range limits, subdivision behavior, and receipt semantics. It is essentially complete for a paid read tool, with only sibling-disambiguation left implicit.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description meaningfully extends two fields: api_key gains payment mechanics (card checkout at /pricing vs x402) that the schema stub lacks, and the description clarifies that the receipt is an answer receipt, not a certified extract.

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 — counting working days in a date range for a country — and specifies the inputs it accounts for (weekends incl. Egypt's Fri–Sat, statutory holidays). It does not, however, differentiate itself from the very close sibling business_days_between, leaving overlap unexplained.

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?

It gives clear context: free evaluation country, paid otherwise, and routes the agent to list_series and verify_answer_receipt explicitly. It also distinguishes itself from the non-MCP certified-extract SKU. It stops short of saying when to prefer this over business_days_between or add_business_days.

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