Blocks

log_sft_answers

Write to the athlete's fatigue-test (SFT) log, read by get_fatigue_tests: their answers, merged with what is there. When the app did not find the test (treadmill, another device), pass hr as they read it — it is recorded by hand and wins over the file's. Name the session by activity_id, or date + sport. Saves on return, no card.

Input Schema

Name	Required	Description
`hr`	No	last-minute HR
`hrr`	No	HR drop in the minute after
`rpe`	No	how hard the test felt
`date`	No
`note`	No
`sport`	No
`activity_id`	No
`minutesLeft`	No	minutes more they could have held it

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedOct 11, 2026

removedInput schema / properties / activity_id / description

Removed value: -"the session that held the test (id from list_activities)"

removedInput schema / properties / date / description

Removed value: -"the test's day, when there is no session id"

changedInput schema / properties / hr / description

Previous value: -"last-minute heart rate, when the app did not read the test"New value: +"last-minute HR"

changedInput schema / properties / hrr / description

Previous value: -"heart-rate drop in the minute after"New value: +"HR drop in the minute after"

changedInput schema / properties / minutesLeft / description

Previous value: -"minutes more they could have held it; rounded to 0.5"New value: +"minutes more they could have held it"

changedInput schema / properties / rpe / description

Previous value: -"how hard the test felt, 0-10"New value: +"how hard the test felt"

removedInput schema / properties / sport / description
```
Removed value: -"with date"
```

Changed6 schema fields changedOct 10, 2026

addedInput schema / properties / date

Added value: +{
+  "description": "the test's day, when there is no session id",
+  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+  "type": "string"
+}

addedInput schema / properties / hr

Added value: +{
+  "description": "last-minute heart rate, when the app did not read the test",
+  "maximum": 230,
+  "minimum": 60,
+  "type": "integer"
+}

addedInput schema / properties / hrr

Added value: +{
+  "description": "heart-rate drop in the minute after",
+  "maximum": 120,
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / note

Added value: +{
+  "maxLength": 300,
+  "type": "string"
+}

addedInput schema / properties / sport

Added value: +{
+  "description": "with date",
+  "enum": [
+    "cycling",
+    "running"
+  ],
+  "type": "string"
+}

removedInput schema / required
```
Removed value: -[
-  "activity_id"
-]
```

Changed3 schema fields changedSep 30, 2026
- addedInput schema / properties / activity_id / description
```
Added value: +"the session that held the test (id from list_activities)"
```
- addedInput schema / properties / minutesLeft / description
```
Added value: +"minutes more they could have held it; rounded to 0.5"
```
- addedInput schema / properties / rpe / description
```
Added value: +"how hard the test felt, 0-10"
```
AddedSep 26, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false. The description adds real behavior beyond that: writes are 'merged with what is there' (non-destructive upsert), manually entered `hr` 'wins over the file's' (precedence rule), and 'Saves on return, no card' (no confirmation interaction). It doesn't cover auth or failure behavior, but the added context is substantive.

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-loads the core action and resource, then layers the conditional hr rule and the naming rule in short, information-dense sentences. Telegraphic style ('no card') costs a little clarity but nothing is padding.

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 an 8-param, no-required-param mutation with no output schema, the description covers the essential write semantics (merge, precedence, session identification, save timing). The gaps are minor since the schema already describes hrr, rpe, and minutesLeft, and no return value needs explaining.

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%: hr, hrr, rpe, and minutesLeft have descriptions, while date, note, sport, and activity_id do not. The description partially compensates by explaining hr's manual-entry precedence and the activity_id vs date+sport session-naming rule, but leaves note and the hrr/rpe semantics to the schema.

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 ('Write to') and resource ('athlete's fatigue-test (SFT) log'), and explicitly names the sibling that reads it back: 'read by get_fatigue_tests'. An agent can distinguish this from log_readiness, log_lactate, and log_session_rpe 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 a clear conditional: 'When the app did not find the test (treadmill, another device), pass `hr` as they read it', plus naming conventions via activity_id or date+sport. It names the read-side sibling but does not spell out when NOT to use this versus the other log_* tools, so it falls short of a full when/when-not/alternatives treatment.

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

All Blocks tools Inspect

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

Need Help?