Skip to main content
Glama
Sign In
YAZIO MCP

YAZIO MCP

by tomastaker
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Nutrition goals

get_goals
Read-onlyIdempotent

Retrieve daily calorie, macro, water, step, and weight goals for any date to plan nutrition and activity targets.

Instructions

Returns calorie, macro, water, step, and weight goals for a date.

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
dateNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare this a safe, read-only, idempotent operation. The description adds value by listing the specific goal categories returned, which is not present in annotations. It does not contradict any annotation.

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 no unnecessary words. It efficiently states the tool's function and scope.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simple nature of the tool (one parameter, output schema present, rich annotations), the description is complete enough. It covers what the tool returns and the time scope, with no need for additional details.

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?

The description mentions 'for a date,' which indicates the purpose of the date parameter, but it does not specify the date format, whether it is optional, or what happens if omitted. With 0% schema coverage, the description only minimally compensates.

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?

The description clearly states the tool returns specific goal types (calorie, macro, water, step, weight) for a date, making its purpose unambiguous and distinct from sibling tools like get_daily_summary or get_water_intake.

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?

The description clearly implies the tool is used to retrieve goals for a specific date, but it does not explicitly mention alternatives or exclusions. However, the context is clear enough for an agent to select this tool when goals are needed.

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