Skip to main content
Glama

HelpySelf

by com.helpyself
OverviewDiscussionsAdmin

Find a Time

find_a_time

Propose a few times, send one link, see when everybody can make it A HelpySelf tool (helpyself.com).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoHow many days the poll link stays open from now. After that it expires.
noteNoA line shown under the title to the people answering, such as where to meet.
titleYesThe heading on the poll page, shown to everybody who opens the link. 'Coffee with the team', 'Board meeting'.
localeNoThe language of the poll page: one of en, de, es, fi, fr, it, nl, pl. Anything else, or nothing, gives English.
optionsYesThe times people choose between, at least 2 and at most 366. Each one is either an object {date, time} or a plain string like "2026-10-20 14:00" or "2026-10-20" for a whole day. Duplicates are refused; they are sorted chronologically for the page.
timezoneNoThe IANA time zone the option times are written in, e.g. 'Europe/Berlin', so the page can say so. Omit it, or give an unknown zone, and the times are shown as written with no zone claimed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / options / description
      Previous value: -"The times people choose between, at least 2 and at most 366. Duplicates are refused; they are sorted chronologically for the page."New value: +"The times people choose between, at least 2 and at most 366. Each one is either an object {date, time} or a plain string like \"2026-10-20 14:00\" or \"2026-10-20\" for a whole day. Duplicates are refused; they are sorted chronologically for the page."
    • addedInput schema / properties / options / items / anyOf
      Added value: +[
+  {
+    "description": "One time to vote on: a date, and optionally a time on it.",
+    "properties": {
+      "date": {
+        "description": "The calendar date of this option, as YYYY-MM-DD.",
+        "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+        "type": "string"
+      },
+      "time": {
+        "description": "The start time on that date, as 24-hour HH:MM. Leave it out to offer the whole day.",
+        "pattern": "^\\d{2}:\\d{2}$",
+        "type": "string"
+      }
+    },
+    "required": [
+      "date"
+    ],
+    "type": "object"
+  },
+  {
+    "description": "The same option written out: \"2026-10-20 14:00\", or \"2026-10-20\" for the whole day.",
+    "pattern": "^\\d{4}-\\d{2}-\\d{2}(?:[T ]\\d{2}:\\d{2}(?::\\d{2})?)?$",
+    "type": "string"
+  }
+]
    • removedInput schema / properties / options / items / description
      Removed value: -"One time to vote on: a date, and optionally a time on it."
    • removedInput schema / properties / options / items / properties
      Removed value: -{
-  "date": {
-    "description": "The calendar date of this option, as YYYY-MM-DD.",
-    "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
-    "type": "string"
-  },
-  "time": {
-    "description": "The start time on that date, as 24-hour HH:MM. Leave it out to offer the whole day.",
-    "pattern": "^\\d{2}:\\d{2}$",
-    "type": "string"
-  }
-}
    • removedInput schema / properties / options / items / required
      Removed value: -[
-  "date"
-]
    • removedInput schema / properties / options / items / type
      Removed value: -"object"
  2. Changed9 schema fields changed
    • addedInput schema / properties / days / description
      Added value: +"How many days the poll link stays open from now. After that it expires."
    • addedInput schema / properties / locale / description
      Added value: +"The language of the poll page: one of en, de, es, fi, fr, it, nl, pl. Anything else, or nothing, gives English."
    • addedInput schema / properties / note / description
      Added value: +"A line shown under the title to the people answering, such as where to meet."
    • addedInput schema / properties / options / description
      Added value: +"The times people choose between, at least 2 and at most 366. Duplicates are refused; they are sorted chronologically for the page."
    • addedInput schema / properties / options / items / description
      Added value: +"One time to vote on: a date, and optionally a time on it."
    • addedInput schema / properties / options / items / properties / date / description
      Added value: +"The calendar date of this option, as YYYY-MM-DD."
    • addedInput schema / properties / options / items / properties / time / description
      Added value: +"The start time on that date, as 24-hour HH:MM. Leave it out to offer the whole day."
    • addedInput schema / properties / timezone / description
      Added value: +"The IANA time zone the option times are written in, e.g. 'Europe/Berlin', so the page can say so. Omit it, or give an unknown zone, and the times are shown as written with no zone claimed."
    • addedInput schema / properties / title / description
      Added value: +"The heading on the poll page, shown to everybody who opens the link. 'Coffee with the team', 'Board meeting'."
  3. Changed1 schema field changed
    • addedInput schema / properties / timezone
      Added value: +{
+  "maxLength": 64,
+  "type": "string"
+}
  4. Changed1 schema field changed
    • changedInput schema / properties / options / maxItems
      Previous value: -30New value: +366
  5. Changed1 schema field changed
    • addedInput schema / properties / locale
      Added value: +{
+  "maxLength": 5,
+  "type": "string"
+}
  6. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false and idempotentHint=false, so the agent already knows this creates state and is not repeat-safe. The description adds that a shareable link is produced and that responses are collected, which is useful beyond the annotations, but 'send one link' is ambiguous about whether the tool actually dispatches the link or just generates a URL, and nothing is said about the limit of one poll per call or what happens on repeat calls.

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 short and front-loaded with the action, which is good, but the sentence is under-specified rather than concise and the 'A HelpySelf tool (helpyself.com)' branding clause earns no place in a tool description.

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?

This is a state-creating tool with no output schema, so the description should explain what comes back (a poll URL? a confirmation?) and how the link is delivered. It gestures at 'one link' but leaves the return value and delivery mechanism undefined, which are the two things an agent must know to complete the workflow.

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% and the schema documents title, options, days, note, locale and timezone thoroughly, including formats and constraints. The description adds no parameter meaning at all, so the baseline 3 applies.

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 concrete verb chain and outcome: 'Propose a few times, send one link, see when everybody can make it,' which conveys a scheduling-poll creator precisely. It never names or contrasts with any sibling (nothing in the list is close, but no differentiation is offered), and the trailing branding clause adds no purpose information.

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 explicit guidance on when to use this versus alternatives, nor any prerequisites (e.g. that it creates a page others must visit, that at least two options are required). The scenario is only implied by the word 'poll'-like phrasing.

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

All HelpySelf 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