Skip to main content
Glama
Sign In

note1

by ai.note1
OverviewDiscussionsAdmin

Get calendar

note1_get_calendar
Read-only

List your calendar events with recording status (which meetings note1 will record).

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": "note1_get_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
teamIdNoAccepted for uniformity; calendar is per-user
upcomingNoDefault true

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare this is a read-only, non-destructive, non-open-world operation. The description adds useful behavioral context by explaining that results include recording status, but it does not mention ordering, pagination, or how the default upcoming behavior affects results.

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 a single front-loaded sentence with zero wasted wording. It clearly communicates the resource and the key returned attribute without unnecessary preamble.

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?

For a simple read-only calendar listing tool, the description covers the core purpose and the recording-status dimension. It remains incomplete about how this differs from meeting-listing siblings and about result limiting/ordering, which are relevant given the limit parameter.

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 67%, with teamId and upcoming documented in the schema while limit is only bounded by minimum/maximum. The description adds no parameter-level meaning beyond what the schema already provides, so the baseline of 3 is appropriate.

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 specific verb and resource: "List your calendar events." It also adds meaningful scope by saying results include "recording status (which meetings note1 will record)." However, it does not distinguish this from siblings such as note1_list_meetings or note1_search_meetings.

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 the purpose: an agent can infer this is the tool for viewing calendar events and their recording status. There is no explicit guidance about when to use it instead of note1_list_meetings, note1_search_meetings, or scheduling-related tools.

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

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