Skip to main content
Glama
Sign In

Connections

by icu.connections
OverviewDiscussionsAdmin

My focus plan for a day

connections_schedule_get_focus_day
Read-only

Read the member's Focus plan for a day: their focus blocks in order (start, end, title, the Notes goal each serves, the mode that says which sites are paused, and whether it is done or skipped), whether it is a day off, whether they checked in or out, and what runs right now.

Input Schema

NameRequiredDescriptionDefault
dateNoThe day, YYYY-MM-DD in the member's own time zone. Default: today.
personNoLinked person to run this call as (first name). Omit to run as the connection's holder.
projectNoWorkspace to run this call in (id or name).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / date / pattern
      Added value: +"^\\d{4}-\\d{2}-\\d{2}$"
  2. Changed1 schema field changed
    • addedInput schema / properties / person
      Added value: +{
+  "description": "Linked person to run this call as (first name). Omit to run as the connection's holder.",
+  "type": "string"
+}
  3. Changed1 schema field changed
    • addedInput schema / properties / project
      Added value: +{
+  "description": "Workspace to run this call in (id or name).",
+  "type": "string"
+}
  4. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description goes beyond them by disclosing the shape of the return payload (block fields, day-off flag, check-in state, current block), which matters since there is no output schema. It stops short of noting empty/missing-plan behavior.

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?

A single front-loaded sentence that immediately names the operation and then lists the payload fields. The parenthetical enumeration is dense but every element carries information about the return value; no filler sentences.

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

Completeness4/5

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

With no output schema, the description usefully compensates by describing what is returned, and all three optional parameters are documented in the schema. Minor gap: it doesn't clarify whose 'member' plan is read when person is omitted, or what a response looks like when there is no plan.

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 coverage is 100% and each parameter (date, person, project) has a clear description, so the baseline is 3. The description adds no extra semantics about the date format, time zone, or the person/workspace scoping beyond what the schema already states.

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?

The description uses a specific verb ('Read') and resource ('the member's Focus plan for a day') and enumerates the contents: ordered focus blocks with start/end/title/goal/mode/completion, day-off status, check-in state, and the current block. No sibling tool overlaps this scope, so an agent can identify it immediately.

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 by 'for a day' and the schema default of today, but the description never says when to prefer this over related tools (e.g. calendar or todo listing) or what to do when no plan exists. It describes content, not invocation context.

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

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