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. 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. 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'."
  2. Changed1 schema field changed
    • addedInput schema / properties / timezone
      Added value: +{
+  "maxLength": 64,
+  "type": "string"
+}
  3. Changed1 schema field changed
    • changedInput schema / properties / options / maxItems
      Previous value: -30New value: +366
  4. Changed1 schema field changed
    • addedInput schema / properties / locale
      Added value: +{
+  "maxLength": 5,
+  "type": "string"
+}
  5. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already signal this is not a read-only tool, and the description adds context by showing it creates a shareable poll link. It does not explicitly state that a persistent poll is created, that the link expires, or what side effects happen server-side, though the schema's days parameter clues the expiry. No contradiction with the annotations.

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?

The description is short, but the phrasing is more of a user-facing tagline than a precise tool definition, and the trailing 'A HelpySelf tool (helpyself.com)' is promotional and adds no value to an AI agent. It could be more effective as one clear sentence such as 'Create a poll link to propose meeting times and collect availability.'

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?

The description covers the key user journey — propose times, share a link, see availability — which is enough to convey what the tool returns. It leaves operational details such as the need for at least two options and the title requirement to the schema, and with no output schema it does not clarify the exact response format beyond 'one link'. An agent can still invoke it using the schema, but the description alone is thin.

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?

The schema already provides 100% description coverage for all six parameters, so the description does not need to explain them. The only parameter-related hint in the description is 'Propose a few times', which loosely maps to options; no additional meaning beyond the schema is added.

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 the core workflow — propose several time options, send one link, and see when everybody can make it — making the tool's purpose as a scheduling-poll creator clear. It is consumer-facing rather than a precise verb+resource statement like 'Create a scheduling poll', but it is specific enough to be distinguished from the many unrelated utilities.

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 description implies the tool should be used when someone wants to coordinate a time that works for multiple people, and no sibling tool has a similar purpose. However, there is no explicit statement of when to use it versus alternatives or what prerequisites exist, so the agent must infer the usage context.

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