Skip to main content
Glama

Bluedose GLP-1 Tools

Next injection site

next_injection_site

Suggest the least recently used of the six common subcutaneous injection sites from a history of sites (most recent last). Rotation helper only: it never recommends or calculates doses.

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

Input Schema

NameRequiredDescriptionDefault
enabledNo
historyNopast sites, most recent last

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the load and does disclose the core algorithm (LRU across a fixed six-site set), the required input ordering, and an important negative capability (no dosing). It does not say what happens with an empty or partial history, nor what the response looks like, which are meaningful gaps for a stateless helper.

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?

Two sentences, zero filler, with the selection rule and the scope limitation front-loaded in that order. Nothing needs to be cut.

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

Completeness3/5

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

A low-complexity two-parameter tool with no output schema, so return values need not be explained. Still, the role of "enabled" and the behavior on empty/partial history are unaddressed, which leaves real ambiguity for correct invocation.

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%, so the baseline is 3. The description reinforces how "history" is consumed (most recent last) and implies the six allowed values, but the "enabled" parameter is never mentioned in either schema or description, leaving an agent to guess whether it scopes which sites are eligible for suggestion.

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 ("Suggest") and resource ("subcutaneous injection sites") plus the exact selection rule: least recently used of six common sites, taken from a history ordered most recent last. The closing clause ("Rotation helper only") further bounds the purpose so an agent can tell it apart from any dose- or tracking-oriented sibling.

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 clear conditions for use (you have a site history, ordered oldest-to-newest) and an explicit exclusion: it never recommends or calculates doses. It does not name an alternative tool for the dosing case, so it stops short of full when/when-not routing.

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