Skip to main content
Glama

Same-Day Time Window Overlap

bpj_time_window_overlap
Read-onlyIdempotent

Find the overlap of two same-day time windows in one time zone.

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": {
      "startA": "<startA>",
      "endA": "<endA>",
      "startB": "<startB>",
      "endB": "<endB>"
    },
    "name": "bpj_time_window_overlap"
  }
}

Input Schema

NameRequiredDescriptionDefault
endAYes
endBYes
startAYes
startBYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so the safety profile needs no restating. The description adds the meaningful constraint that both windows must be on the same day in a single zone, but is silent on the no-overlap case (empty result vs. error) and on whether endpoints are inclusive. With annotations carrying the safety burden, this is adequate but thin.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though its brevity contributes to the behavioral and parameter gaps elsewhere.

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 small pure computation over four string inputs with no output schema, the definition covers the core operation but leaves key questions open: result shape when there is no overlap, endpoint inclusivity, and input format. These are the differences an agent actually needs to call it correctly.

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%, so the description bears the full load for four required parameters, yet it adds no meaning beyond the schema's field titles. It never states the expected time format, ordering (start before end), or what happens when a start exceeds its end.

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 concrete verb and resource: 'find the overlap of two same-day time windows'. That is unambiguous and lets an agent identify the operation without opening the schema. It does not name or differentiate against any sibling, so it falls 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 Guidelines3/5

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

The 'same-day' and 'one time zone' qualifiers implicitly bound when the tool applies (not across days, not across zones), which is useful inferable guidance. However, there is no explicit statement of when to prefer this over other time tools or what to do if the windows do not overlap.

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.