Skip to main content
Glama
Sign In
gwagent

gwagent

by vcnngr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

calendar_working_location

Get the scheduled working location (Office, Home, etc.) for specified dates. This tool retrieves location data directly from the calendar application to aid in trip planning or task scheduling.

Instructions

Your working location (Office, Home, ...) for each day, as shown by the Calendar app.

Working locations are not in the provider. Days without one are reported with place null.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "calendar_working_location"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoFirst day: YYYY-MM-DD, today, tomorrow...today
daysNoNumber of days (1-31).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that working locations are not in the provider and that missing days are reported with place null, but it does not state read-only status, permissions, or the full output shape.

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?

Two short sentences, front-loaded with the resource and followed by useful caveats about provider absence and null place values. No filler or repetition.

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 tool is low-complexity and the schema is fully described, but no output schema exists. The description mentions the null edge case yet does not fully describe the return structure or confirm read-only behavior, leaving modest gaps for an agent.

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 date and days are already documented in the schema. The description reinforces the per-day nature but adds no parameter-specific format or behavior beyond what the schema provides.

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 identifies the resource: daily working locations from the Calendar app, with example values (Office, Home). It does not explicitly name the read/list action or distinguish itself from the sibling calendar_set_working_location, but the intended data is clear.

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?

It implies the tool is for viewing working locations, but gives no explicit when-to-use guidance, prerequisites, or exclusions. Critically, it does not tell the agent to use calendar_set_working_location when changing a location instead.

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

Deploy Server

Other Tools