Skip to main content
Glama
Sign In

Sigwren

by com.sigwren
OverviewDiscussionsAdmin

A page to upload a clip for a free running-form check

get_form_check_link
Destructive

A link to a Sigwren page where a runner uploads one short clip of themselves running (side-on, 30 seconds or less) for a free running-form check. Sigwren reads the clip once and gives back what the runner does well, what to work on, one focus with a drill, and cues to run with. The clip is deleted as soon as it has been read, and the full read is emailed to the address the runner gives on the page. Each email address gets one free check. The page asks for the clip, an email address, and a tick to confirm the clip is the runner, that they are 18 or over, and that anyone else in it agreed to be filmed. Afterwards, get_test_result with this link returns a summary for the assistant to explain. Each call makes a new link. It needs no account. With the person's "Check with me first" setting on (the default), a call without a confirmation makes no change: it returns a description of the change and a confirmation value, and the change is held for the person to approve. The same call with that confirmation value makes it. With the setting off, the change is made straight away.

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_form_check_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmationNoThe confirmation value from an earlier call of this tool with the same arguments, once the person has approved the change it described. Without it, Sigwren describes the change and makes none.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Discloses a great deal beyond the annotations: no account required, one free check per email address, the clip is deleted immediately after reading, the full read is emailed to the supplied address, and each call mints a new link (consistent with idempotentHint=false). It also spells out the approve-first confirmation protocol, including that an unconfirmed call makes no change and returns a change description plus a confirmation value.

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?

The core purpose is front-loaded in the first sentence and every subsequent sentence adds real information (privacy, limits, downstream use, confirmation flow). It is dense and slightly repetitive about the confirmation protocol, which the schema already documents, keeping it short of a 5.

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

Completeness5/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 return-value burden and does so: it returns a link, or, for an unconfirmed call, a description of the change plus a confirmation value. Privacy, eligibility limits, and the downstream call are all covered, so an agent has everything needed to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description reinforces the meaning of the single `confirmation` parameter by explaining both branches (without it, nothing changes; with it, the change is applied). That adds usable semantic context rather than restating 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?

States a specific resource (a link to a Sigwren upload page) and the exact purpose (one short side-on clip, 30s or less, for a free running-form check). It is not explicitly differentiated from the similar-sounding sibling get_test_upload_link, which an agent could easily confuse it with, but it does name the downstream get_test_result.

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?

Makes clear this is the entry point for a free running-form check and that get_test_result consumes the resulting link afterwards. The confirmation/approval flow is explained with both the default-on and default-off cases. It lacks an explicit 'use this instead of get_test_upload_link when...' routing statement.

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

All Sigwren 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