Skip to main content
Glama

Dayze — Life Context

Update Sleep

update_sleep

Sleep: patch an existing sleep record by sleep_id. ($0.10; API key required)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "sleep_id": "<sleep_id>"
    },
    "name": "update_sleep"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNoFree-text note, e.g. Follow up next week.
qualityNoSleep quality rating, e.g. 4.
ended_atNoEnd as ISO date-time, e.g. 2026-10-17T07:00:00+08:00.
sleep_idYesSleep record id, e.g. 3f2a1b4c-8d9e-6f01-c2b3-c4d5e6f70809.
timezoneNoIANA time zone, e.g. America/Los_Angeles.
request_idNoClient idempotency key (retries return original result).
sleep_typeNoSleep record type: overnight, nap or unknown, e.g. overnight.
started_atNoStart as ISO date-time, e.g. 2026-10-16T23:00:00+08:00.
idempotency_keyNoAlias for request_id.

Output Schema

NameRequiredDescriptionDefault
okNo
sleepNo
accountNoThe Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.
messageNo
provenanceNoWhich connector wrote the record and which connected Dayze account received it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / properties / ended_at / description
      Added value: +"End as ISO date-time, e.g. 2026-10-17T07:00:00+08:00."
    • addedInput schema / properties / notes / description
      Added value: +"Free-text note, e.g. Follow up next week."
    • addedInput schema / properties / quality / description
      Added value: +"Sleep quality rating, e.g. 4."
    • addedInput schema / properties / sleep_id / description
      Added value: +"Sleep record id, e.g. 3f2a1b4c-8d9e-6f01-c2b3-c4d5e6f70809."
    • addedInput schema / properties / sleep_type / description
      Added value: +"Sleep record type: overnight, nap or unknown, e.g. overnight."
    • addedInput schema / properties / started_at / description
      Added value: +"Start as ISO date-time, e.g. 2026-10-16T23:00:00+08:00."
    • addedInput schema / properties / timezone / description
      Added value: +"IANA time zone, e.g. America/Los_Angeles."
  2. Changed2 schema fields changed
    • addedOutput schema / properties / account
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "The Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.",
      +  "properties": {
      +    "display_name": {
      +      "description": "Account display name.",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "handle": {
      +      "description": "Account handle, e.g. @goh.",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "note": {
      +      "description": "How to disclose the account to the user.",
      +      "type": "string"
      +    },
      +    "qa_fixture": {
      +      "description": "True for a known QA test account: its records are fixture data, not a real life.",
      +      "type": "boolean"
      +    }
      +  },
      +  "required": [
      +    "handle",
      +    "display_name",
      +    "qa_fixture",
      +    "note"
      +  ],
      +  "type": "object"
      +}
    • addedOutput schema / properties / provenance
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "Which connector wrote the record and which connected Dayze account received it.",
      +  "properties": {
      +    "account": {
      +      "additionalProperties": false,
      +      "description": "The Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.",
      +      "properties": {
      +        "display_name": {
      +          "description": "Account display name.",
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "handle": {
      +          "description": "Account handle, e.g. @goh.",
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "note": {
      +          "description": "How to disclose the account to the user.",
      +          "type": "string"
      +        },
      +        "qa_fixture": {
      +          "description": "True for a known QA test account: its records are fixture data, not a real life.",
      +          "type": "boolean"
      +        }
      +      },
      +      "required": [
      +        "handle",
      +        "display_name",
      +        "qa_fixture",
      +        "note"
      +      ],
      +      "type": "object"
      +    },
      +    "channel": {
      +      "description": "Always mcp_connector.",
      +      "type": "string"
      +    },
      +    "connector": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "kind": {
      +          "description": "oauth or api_key.",
      +          "type": "string"
      +        },
      +        "name": {
      +          "description": "The connected app or API-key label shown to the account owner.",
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "kind",
      +        "name"
      +      ],
      +      "type": "object"
      +    },
      +    "source": {
      +      "description": "chatgpt for ChatGPT OAuth writes; mcp for another OAuth app or API key.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "source",
      +    "channel",
      +    "connector",
      +    "account"
      +  ],
      +  "type": "object"
      +}
  3. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally; the description adds genuinely useful context by disclosing the per-call cost ($0.10) and API-key requirement. It does not, however, state whether omitted fields are preserved on patch or what a successful response contains, so the added value is real but limited.

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?

One sentence plus a bracketed cost/auth note, with the operation and key front-loaded. Nothing is padded beyond the redundant "Sleep:" label, which is minor.

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?

For a simple patch tool with a fully documented 9-parameter schema, an output schema, and full annotations, the description covers the operational essentials plus cost and auth. The only meaningful gap is patch merge semantics for omitted fields, which is left implicit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and every parameter carries an example, so the schema does the heavy lifting and the baseline of 3 would apply. The description adds slight value by naming sleep_id as the addressing key for the operation, reinforcing that the other eight fields are optional patch targets.

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?

States a specific verb ("patch") and resource ("sleep record") plus the identifying key (sleep_id), which distinguishes it from get_sleep and log_sleep by implication. It stops short of explicitly naming the sibling it replaces, and the redundant "Sleep:" prefix adds nothing.

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?

"Patch an existing sleep record by sleep_id" implies the record must already exist and that this is a partial update rather than a create, but there is no explicit when-to-use guidance, no when-not conditions, and no named alternative for creating a record (e.g., log_sleep).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.