Skip to main content
Glama

Canonical UTC timestamp check

bpj_dq_utc_timestamps
Read-onlyIdempotent

Check UTC timestamps with seconds, optional three-digit milliseconds and a literal Z.

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": {
      "rows": "<rows>",
      "column": "<column>"
    },
    "name": "bpj_dq_utc_timestamps"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsYes
columnYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds the validation criteria (required seconds, optional three-digit milliseconds, literal Z), but does not disclose what an invalid result looks like or how the check reports failures.

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?

The description is a single front-loaded sentence with no filler or repetition. It is appropriately compact, though it is terse enough that the agent receives no structural cues about usage or outcome.

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 two-parameter data-quality check with no output schema and zero parameter descriptions, the definition is under-specified. It states the validation pattern but omits how rows and column are used, what the tool returns, and when to choose it over sibling checks.

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

Parameters1/5

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

Schema description coverage is 0% for both parameters, and the description does not mention 'rows' or 'column' at all. It adds no meaning about which column is checked, how rows should be formatted, or what limits apply beyond what the bare schema titles already show.

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: 'Check UTC timestamps' plus the exact accepted pattern (seconds, optional three-digit milliseconds, literal Z). It is clear what the tool validates, though it does not explicitly distinguish itself from sibling checks such as bpj_convert_timestamp or other dq tools.

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 named alternative. An agent is left to infer that this is the right data-quality check for a UTC timestamp column rather than a conversion or other validation tool.

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.