Skip to main content
Glama
Sign In

Vitalli

by app.vitalli.mcp
OverviewDiscussionsAdmin

joiva_set_macro_targets

DestructiveIdempotent

Set the signed-in user's macro philosophy and targets. Semantics differ per macro: protein is a floor (at least X g), carbsMaxG a cap (at most; null = no cap), fat fills the remaining calorie budget automatically. clear=true removes the configuration.

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

Input Schema

NameRequiredDescriptionDefault
clearNoRemove the stored macro targets
proteinGNoProtein floor in grams; preset default when omitted
carbsMaxGNoCarb cap in grams; null = explicitly no cap; preset default when omitted
philosophyNoRequired unless clear=true

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true; the description adds real context on top of that by stating exactly what clear=true destroys (the stored configuration) and that fat is auto-derived from the remaining calorie budget. It doesn't say whether existing targets are overwritten wholesale or merged, which keeps it short of a 5.

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?

Three sentences, front-loaded with the core action, then the per-macro semantics, then the destructive clear path. Every clause carries information and no sentence repeats structured fields verbatim.

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 4-parameter destructive, idempotent mutation with no output schema, the description covers what is written, how the fields interact, and how to remove the configuration. It omits confirmation/return behavior after a successful set, a minor gap given how compact the tool is.

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 baseline is 3, but the description adds genuine meaning beyond the schema: it explains the directional semantics per macro (protein is a floor, carbsMaxG is a cap, fat is computed, not supplied). This resolves how the four numeric inputs interact, which the schema documents only in isolation.

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+resource+scope: sets the signed-in user's macro philosophy and targets. An agent can distinguish this from the read-only sibling joiva_get_macro_targets 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 Guidelines3/5

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

The description implies usage through the per-macro semantics and the clear=true removal path, but never says when to call this versus joiva_get_macro_targets or how to choose a philosophy preset. Context is implied rather than stated, and there are no explicit exclusions.

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

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