Skip to main content
Glama
Sign In

Dayze — Life Context

by com.dayze
OverviewDiscussionsAdmin

Reopen To-do

reopen_todo

Reopen one done to-do by exact todo_id. ($0.05; 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": {
      "todo_id": "<todo_id>"
    },
    "name": "reopen_todo"
  }
}

Input Schema

NameRequiredDescriptionDefault
todo_idYesExact id from get_todos or create_todo. Titles are not accepted.
request_idNoClient idempotency key (retries return original result).
idempotency_keyNoAlias for request_id.

Output Schema

NameRequiredDescriptionDefault
todoNo
accountNoThe Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.
changedYes
messageYes
todo_idYes
verifiedYes
provenanceNoWhich connector wrote the record and which connected Dayze account received it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare that this is a non-read-only, non-destructive, closed-world operation. The description adds useful context beyond the annotations by disclosing the cost ($0.05) and the API key requirement, plus the precondition that the to-do must be done, though it does not describe what happens if the to-do is not currently done.

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 definition is two short sentences with the core operation front-loaded and no wasted wording. The cost and auth note is compactly parenthesized.

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 state-transition tool with full schema descriptions, annotations, and an output schema, the description is largely complete: it states the operation, target, precondition, and cost/auth requirements. It could add what happens when the to-do is not in a done state, but that is a minor gap.

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 the schema already explains that todo_id must be an exact id from get_todos or create_todo and that titles are not accepted. The description reinforces 'exact todo_id' but adds no new format, validation, or idempotency details beyond the schema.

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: 'Reopen one done to-do'. It also constrains the target to an exact todo_id, which makes the operation distinguishable from complete_todo and update_todo at a high level, though it does not name those siblings explicitly.

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 'done to-do' and 'exact todo_id', which tells the agent to use this only for completed items identified by id. It does not explicitly say when to prefer complete_todo or update_todo instead, nor does it describe exclusions or error conditions.

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

All Dayze — Life Context 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