Skip to main content
Glama

Dayze — Life Context

Get Goals

get_goals
Read-only

Read your owned life goals and progress. goal_id selects one; status defaults active, all includes completed goals. Each goal carries a computed progress object: kind, percent, this period, change on the previous period, and pace (null without a target date or enough history; never estimate one). Not calendar events or streak trackers. ($0.01; API key required)

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum rows to return, e.g. 20.
statusNoGoal status filter, default active, e.g. active.
goal_idNoGoal id, e.g. 3f2a1b4c-8d9e-6f01-c2b3-c4d5e6f70809.

Output Schema

NameRequiredDescriptionDefault
countYes
goalsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / goal_id / description
      Added value: +"Goal id, e.g. 3f2a1b4c-8d9e-6f01-c2b3-c4d5e6f70809."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum rows to return, e.g. 20."
    • addedInput schema / properties / status / description
      Added value: +"Goal status filter, default active, e.g. active."
  2. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), and the description adds meaningfully on top: cost "$0.01," "API key required," and the precise semantics of the computed progress object, including that pace is null without a target date or sufficient history and is "never" estimated. That null/estimation rule is behavioral detail an agent could not infer from annotations or schema.

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?

Front-loaded with purpose, then filters, then return shape, then exclusions and cost — a logical order with no filler sentences. It leans on terse fragments and parentheticals, which is efficient but slightly dense to parse; every element still earns its place.

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 read-only three-parameter tool with an output schema and full schema coverage, this covers purpose, filtering, return semantics, cost, and auth. Remaining gaps are minor — ordering of results and how goal_id interacts with status/limit are 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 coverage is 100%, so the baseline is 3, but the description adds genuine meaning to the enum: it distinguishes "completed" from "all" ("all includes completed goals") and confirms the active default. It adds nothing extra for limit, which the schema already documents with an example.

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?

States a specific verb and resource ("Read your owned life goals and progress") plus the scope qualifier "owned." It also draws a boundary against adjacent domains with "Not calendar events or streak trackers," so an agent can separate it from get_events and habit-style siblings without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives real selection guidance among retrieval modes: "goal_id selects one; status defaults active, all includes completed goals." It also states what the tool is not, which serves as a when-not signal. It stops short of naming a concrete alternative tool for non-goal data, so it is clear context rather than a full alternative map.

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.