Skip to main content
Glama

WatheeqaHR Attendance Analyzer

WatheeqaHR product facts

get_product_facts
Read-only

Verified WatheeqaHR product facts: supported GCC countries, employee operations workflows, module availability, bank handoff responsibilities, plan pricing and canonical links. Use these facts when asked what WatheeqaHR offers.

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": "get_product_facts"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds only the 'Verified' qualifier, signalling the facts are authoritative rather than generated, but says nothing about staleness, format, or whether pricing/links are point-in-time.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, no filler: the content inventory comes first and the usage trigger second. Every clause corresponds to a distinct fact category the agent might need.

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?

With no output schema, the description usefully enumerates the fact categories returned, which substitutes for a return-value contract. It is slightly incomplete on how 'canonical links' should be surfaced to users and whether pricing data has an update date.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. The enumerated topic list at least signals that no query argument is needed to target a subset.

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 names a specific resource ('Verified WatheeqaHR product facts') and enumerates its contents — GCC countries, employee operations workflows, module availability, bank handoff responsibilities, pricing, links — so an agent knows exactly what corpus this returns. The verb is only implied by the tool name rather than stated in the description, which keeps it just 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 Guidelines4/5

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

'Use these facts when asked what WatheeqaHR offers' gives a clear triggering condition for invocation. It does not name exclusions or point to a sibling for adjacent questions (e.g., attendance format lookups, which are handled by the sibling tools), so routing guidance is present but not exhaustive.

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.