Skip to main content
Glama
Sign In

Sliq

by com.getsliq
OverviewDiscussionsAdmin

Resolve date

resolve_date
Read-only

Also use this to convert times in other timezones to the user's local timezone. For example, if someone says "2pm PST" and the user is in Eastern, call resolve_date("2pm PST") and it will return the equivalent time in the user's timezone. Use standard timezone abbreviations (PST, PDT, EST, EDT, CST, CDT, MST, MDT, GMT, UTC, etc.) -- "Pacific" or "Eastern" alone won't parse.

IMPORTANT: When using the result for trigger_at in add_trigger, ALWAYS use the utc_iso field from the response (e.g. "2026-04-04T04:56:00Z"). The time and time_12h fields are in the user's LOCAL timezone — passing them with a "Z" suffix will create triggers at the wrong time. Dict with date, weekday, and (when time is present) time, time_12h, and utc_iso (UTC ISO format for use in triggers).

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": {
      "expression": "<expression>"
    },
    "name": "resolve_date"
  }
}

Input Schema

NameRequiredDescriptionDefault
expressionYesNatural language date/time expression (e.g. "Tuesday", "next Monday", "2pm PST", "3:30 PM EDT Thursday")
relative_toNoThe timestamp in the `<sliq_sent_at>` of an earlier message the expression came from, e.g. "2026-09-26T16:08-04:00". Omit to count from now.
on_behalf_ofNoA teammate's email, or an agency client's from list_agency_clients, to run this call in that account: their agents, settings, connected accounts, and credits. Omit it to act on your own account.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / on_behalf_of / description
      Previous value: -"An agency client's email, from list_agency_clients, to run this call in that client's account: their agents, settings, connected accounts, and credits. Omit it to act on your own account."New value: +"A teammate's email, or an agency client's from list_agency_clients, to run this call in that account: their agents, settings, connected accounts, and credits. Omit it to act on your own account."
  2. Changed1 schema field changed
    • addedInput schema / properties / relative_to
      Added value: +{
+  "anyOf": [
+    {
+      "format": "date-time",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "The timestamp in the `<sliq_sent_at>` of an earlier message the\nexpression came from, e.g. \"2026-09-26T16:08-04:00\". Omit to count from now."
+}
  3. Changed1 schema field changed
    • addedInput schema / properties / on_behalf_of
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "An agency client's email, from list_agency_clients, to run this call in that client's account: their agents, settings, connected accounts, and credits. Omit it to act on your own account."
+}
  4. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations only declare readOnlyHint=true, so the description's main added value is the warning that `time`/`time_12h` are in the user's LOCAL timezone while `utc_iso` is UTC, and that appending 'Z' to local fields causes wrong trigger times. That is genuine behavioral disclosure beyond the annotations. It stops short of describing defaulting behavior when relative_to is omitted (other than 'count from now') or how ambiguous expressions are handled.

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 core purpose and the routing sentence are front-loaded, and the returns block is warranted since no output schema exists. It is somewhat long and slightly repetitive (the timezone example is restated in prose and again in the IMPORTANT warning), but every section carries actionable content rather than filler.

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

Completeness5/5

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

For a 3-parameter read-only resolver with no output schema, the description covers purpose, call-site triggers, format constraints, return fields, and the critical local-vs-UTC pitfall. An agent can call this correctly and consume the result without inspecting anything else.

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

Parameters3/5

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

Schema description coverage is 100%, so both expression and the two optional parameters are already documented in the schema, making 3 the baseline. The description does add parsing guidance for the expression parameter (accepted timezone abbreviations) that the schema lacks. However, it never mentions `relative_to` or `on_behalf_of`, leaving those entirely to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a precise verb+resource pair: resolve a natural language or relative date/time expression into a concrete date and optional time. It also carves out a second distinct capability (timezone conversion) and names concrete downstream consumers like create_calendar_event, so it is unmistakable against siblings such as search_calendar or add_trigger.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly says when to call it (before search queries, create_calendar_event, or any operation needing a concrete date) and gives a separate trigger for the timezone-conversion case. It also states a hard parsing constraint — use standard abbreviations like PST/EDT because 'Pacific' or 'Eastern' alone won't parse — which prevents a whole class of failed calls.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Sliq toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources