Skip to main content
Glama
ref-tools

Widget MCP

by ref-tools
OverviewSchemaRelated ServersScoreDiscussions
Hybrid

Timer

timer

Set a timer for any task by entering the duration in seconds. The Widget MCP server integrates interactive tools into chats, providing visual timers for efficient time management.

Instructions

Start a timer. You don't need to say anything else after answering with this tool.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
durationYesThe duration of the timer in seconds

Implementation Reference

  • index.ts:15-37 (registration)
    Registration of the 'timer' MCP tool, including schema and handler function.
    server.registerTool(
  "timer",
  {
    title: "Timer",
    description:
      "Start a timer. You don't need to say anything else after answering with this tool.",
    inputSchema: {
      duration: z.number().describe("The duration of the timer in seconds"),
    },
  },
  async ({ duration }) => {
    const timerResource = createTemplatedUIResource(
      createUIResource,
      "ui://widget/timer",
      timerHtml,
      { duration, mode: "timer" }
    );

    return {
      content: [timerResource],
    };
  }
);
  • index.ts:25-37 (handler)
    Handler function that creates a templated UI resource for the timer widget based on the input duration.
      async ({ duration }) => {
    const timerResource = createTemplatedUIResource(
      createUIResource,
      "ui://widget/timer",
      timerHtml,
      { duration, mode: "timer" }
    );

    return {
      content: [timerResource],
    };
  }
);
  • index.ts:17-24 (schema)
    Input schema definition for the 'timer' tool using Zod, specifying the duration parameter.
    {
  title: "Timer",
  description:
    "Start a timer. You don't need to say anything else after answering with this tool.",
  inputSchema: {
    duration: z.number().describe("The duration of the timer in seconds"),
  },
},

Tool Definition Quality

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions that 'You don't need to say anything else after answering with this tool', which hints at a silent or automated post-invocation behavior, but doesn't clarify key aspects like whether the timer runs in the background, how it notifies upon completion, or if it's interruptible. This leaves significant gaps in understanding the tool's behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise with two short sentences that are front-loaded: the first states the core purpose, and the second provides a usage note. There is no wasted text, and every sentence serves a clear purpose, making it highly efficient.

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?

Given the tool's simplicity (one parameter, no output schema, no annotations), the description is incomplete. It lacks details on behavioral traits (e.g., how the timer operates or notifies), doesn't explain the return values or any post-invocation effects beyond a vague hint, and fails to address potential complexities like error handling or duration limits, leaving the agent with insufficient context for reliable use.

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 description coverage is 100%, with the single parameter 'duration' clearly documented in the schema as 'The duration of the timer in seconds'. The description doesn't add any additional meaning or context beyond what the schema provides, such as acceptable ranges or units, so it meets the baseline for high schema coverage without compensating value.

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 clearly states the action ('Start a timer') and identifies the resource (timer), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'stopwatch' or 'conversion', which could have overlapping timing functionality.

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?

The description provides minimal guidance with 'You don't need to say anything else after answering with this tool', which suggests a post-invocation behavior but doesn't offer when to use this tool versus alternatives like 'stopwatch'. No explicit when/when-not scenarios or sibling tool comparisons are provided.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ref-tools/widget-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server