Skip to main content
Glama

Bluedose GLP-1 Tools

Days until shot day

shot_day_countdown

Days until the next weekly shot day (0 = today) for a weekday and a reference date. A countdown only.

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": {
      "shot_day": "<shot_day>"
    },
    "name": "shot_day_countdown"
  }
}

Input Schema

NameRequiredDescriptionDefault
todayNoYYYY-MM-DD, default today (UTC)
shot_dayYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose key behavior: pure countdown semantics, weekly recurrence, and that 0 means today. It does not state the output range (presumably 0-6), whether results can be negative, or that the operation is side-effect free — reasonable inferences but not stated.

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?

Two short sentences with the core computation front-loaded and no wasted wording. 'A countdown only' is terse to the point of being slightly cryptic, which keeps it just short of a 5.

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 two-parameter computation with no output schema, the description covers the essential semantics: what is counted, the reference date, and the 0 = today boundary. The main omission is the expected numeric range of the return value, which is a minor gap for a tool this simple.

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 50%: today is documented as YYYY-MM-DD with UTC default, while shot_day relies on its enum. The description's 'for a weekday and a reference date' maps the two parameters to their roles, which adds a little clarity, but no format or edge-case detail 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 names a specific computation: days remaining until the next weekly shot day, parameterized by a weekday and a reference date. That is clearly distinct from siblings like next_injection_site and glp1_search_interest, though the differentiation is implicit rather than stated.

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

Usage Guidelines2/5

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

The phrase 'A countdown only' is a scope limitation, hinting it isn't for scheduling or reminders, but there is no explicit when-to-use guidance and no named alternative or exclusion. An agent must infer the intended context from the tool name alone.

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.

Resources