Skip to main content
Glama

WritersLogic business agents

temporal-constraints

Are these timing constraints satisfiable? Earliest/latest time per event, or the conflicting constraints — Solves a simple temporal network: up to 40 named time points, up to 200 difference constraints 'b is between min and max minutes after a' and optional fixed instants, relative to a caller origin instant. When consistent it returns each point's earliest and latest feasible instant (where bounded); when not, it returns the cycle of constraints that contradict each other, with the total impossible sl

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": {
      "origin": "<origin>",
      "points": "<points>",
      "constraints": "<constraints>"
    },
    "name": "temporal-constraints"
  }
}

Input Schema

NameRequiredDescriptionDefault
fixedNo
originYesInstant that point 'origin' (an implicit extra point) is at; all minutes are relative to it.
pointsYes
constraintsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does disclose real behavior: input limits, optional fixed instants, that all minutes are relative to a caller-supplied origin, and the two distinct outcomes (per-point earliest/latest windows when consistent, the contradictory constraint cycle when not). The final sentence is cut off mid-word, so the description of the infeasible-case payload ('total impossible sl...') is left dangling, which is the main transparency gap.

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?

It is front-loaded with the core question, which is good, but the prose is telegraphic and the trailing clause is truncated mid-word, so the description literally does not finish. The middle sentence is dense but earns its place by packing the model, limits, and origin semantics.

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?

There is no output schema and no annotations, so the description must explain both inputs and returns. It handles the input model and the consistent-case return well, but the inconsistent-case return is left incomplete by the truncation, and nothing is said about error behavior or how the cycle is expressed.

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 description coverage is low (25%), so the description must compensate, and it does: it explains that 'b is between min and max minutes after a' defines the constraint direction and units, that points are 'named time points', that 'fixed' provides optional fixed instants, and that origin is an implicit extra point all minutes are measured from. It adds no guidance on the 'id' field on constraints, leaving that one parameter undocumented in both places.

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 opens with a concrete question ('Are these timing constraints satisfiable?') and then names the specific computation: solving a simple temporal network over named time points with difference constraints. That is a specific verb+resource, not a restatement of the tool name. It does not contrast itself with any sibling, but the purpose is unmistakable.

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?

Usage is implied rather than stated: the agent can infer this is for feasibility checking of min/max separation constraints plus optional fixed instants, and the size caps (40 points, 200 constraints) implicitly mark the tool's boundary. There is no explicit when-to-use, when-not-to-use, or pointer to an alternative for larger or differently-shaped problems.

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