ZeroPhase

log_pst

Log a PST result (the Navy Physical Screening Test): 500-yard swim, 2-minute push-ups, 2-minute sit-ups, max pull-ups, 1.5-mile run. The new result recalibrates the daily plan.

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": {
      "swim_time": "<swim_time>",
      "pushups": "<pushups>",
      "situps": "<situps>",
      "pullups": "<pullups>",
      "run_time": "<run_time>"
    },
    "name": "log_pst"
  }
}

Input Schema

Name	Required	Description
`date`	No	The test date, yyyy-MM-dd. Default: today (US Eastern).
`notes`	No	Notes on the test. Optional.
`situps`	Yes	Sit-ups in 2 minutes.
`pullups`	Yes	Pull-ups, max, no time cap.
`pushups`	Yes	Push-ups in 2 minutes.
`run_time`	Yes	1.5-mile run, MM:SS.
`swim_time`	Yes	500-yard swim, MM:SS.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations declare only that this is a non-read-only, non-destructive, non-open-world write. The description adds a genuinely non-obvious behavioral consequence beyond that: 'The new result recalibrates the daily plan,' telling the agent the write has downstream effects on other tools' outputs. It leaves gaps on whether a second log for the same date overwrites or appends, and whether the recalibration is immediate.

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 tight sentences, front-loaded with the action and its scope, then the downstream effect. The event enumeration is mildly redundant with the schema's parameter names, but it earns its place by identifying what a PST actually is.

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 7-parameter write tool with full schema coverage and no output schema, the definition covers what the tool does and its main side effect. Remaining gaps are duplicate-date semantics and what the caller gets back (scores? recalculated plan?), which would matter for an agent logging repeats.

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 description coverage is 100% — every parameter already carries a description including units and format (MM:SS, 2-minute caps, today default). The description's event list mirrors the same five required parameters without adding format or constraint detail, so the schema does the heavy lifting and the baseline of 3 applies.

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?

States a specific verb+resource ('Log a PST result') and immediately disambiguates the acronym into the five scored events, so an agent knows this is a full fitness-test result rather than an individual workout. It does not name the sibling tools (log_cardio, log_exercise) it must be distinguished from, so it stops short of a 5.

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?

Usage is only implied: the enumerated test events signal that this is for a complete PST scoring, not a single cardio or strength entry, which is enough to route an agent away from log_cardio/log_exercise. There is no explicit when-to-use statement, no prerequisite (e.g., that all five events must be supplied), and no note on how it relates to list_pst_results or get_pst_result.

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

All ZeroPhase 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?