Skip to main content
Glama
Sign In

Morris Golf

by golf.morris
OverviewDiscussionsAdmin

Get my drill activity

get_my_drill_activity
Read-onlyIdempotent

Read what the player does in the drill library themselves (app, WhatsApp, Thursday's video), per improvement area with the most watched first: clips viewed, finished, skipped, opened in full, saved and practised. Use it to see what they keep coming back to; for scored drill results use get_practice_progress. What an assistant logs with log_drill_event is not counted here. Read-only.

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

Input Schema

NameRequiredDescriptionDefault
daysNoOnly the last N days, and then saved and practised count only what was marked inside them. Default 60; 0 is the whole history.
langNoLanguage of titles and steps: es, en, fr, de, it, pt, nl, sv, da, fi, no or ja. Default es; pass the player's language.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / days / description
      Added value: +"Only the last N days, and then saved and practised count only what was marked inside them. Default 60; 0 is the whole history."
    • addedInput schema / properties / lang / description
      Added value: +"Language of titles and steps: es, en, fr, de, it, pt, nl, sv, da, fi, no or ja. Default es; pass the player's language."
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive/closed-world, so the trailing 'Read-only' is largely redundant. The description does add genuinely non-obvious behavior beyond annotations: that assistant-logged drill events from log_drill_event are excluded from the counts, and that results are ordered by watch frequency. It does not describe cardinality or pagination for the per-area result set.

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?

Purpose and metric list are front-loaded in the first sentence, followed by routing guidance and the log_drill_event caveat. Minor waste in the parenthetical channel enumeration '(app, WhatsApp, Thursday's video)' and the redundant closing 'Read-only', but overall every sentence carries routing or scoping value.

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?

With no output schema, the description carries the burden of describing return values and does so by naming the metric fields, the grouping dimension, and the sort order. It omits the shape of area labels (mitigated by the lang parameter) and any result-size expectations, but is sufficient 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 description coverage is 100%, so both parameters (days window semantics including the 0 = all-history edge case, and the lang enum) are already fully documented in the schema. The description adds nothing specific about days or lang beyond what the schema states, so baseline 3 applies.

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 and resource ('Read what the player does in the drill library themselves') and enumerates the exact metrics returned: clips viewed, finished, skipped, opened in full, saved and practised. It also names the grouping ('per improvement area') and ordering ('most watched first'), so an agent can distinguish it from get_practice_progress without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit use case ('Use it to see what they keep coming back to'), an explicit alternative with its selection condition ('for scored drill results use get_practice_progress'), and an explicit exclusion ('What an assistant logs with log_drill_event is not counted here'). This is the full when/when-not/alternative triad.

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

All Morris Golf 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