ThumbGate

Track Action

track_action

Destructive

Record verification actions in the current session, such as figma_verified or tests_passed, to create a time-limited log of evidence. Actions expire after one hour.

Instructions

Record a verification action in the current session (for example figma_verified or tests_passed). Session actions expire after one hour.

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": {
      "actionId": "<actionId>"
    },
    "name": "track_action"
  }
}

Input Schema

Name	Required	Description	Default
`actionId`	Yes	Verification action ID to record
`metadata`	No	Optional structured metadata describing the evidence source

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.23.1May 25, 2026
Removedv1.21.2May 20, 2026
Addedv1.16.9May 3, 2026

TDQS

A4/5.0

Behavior3/5

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

Description adds expiry information beyond annotations ('Session actions expire after one hour'), but does not elaborate on the destructive hint (e.g., whether it overwrites previous actions, irreversibility, or required permissions). Annotations only provide destructiveHint=true without further context.

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 with no extraneous information. Purpose is front-loaded, and the expiry detail is a necessary addition. Every sentence adds 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?

Given two parameters, one required, no output schema, the description covers core purpose, examples, and time-bound behavior. It assumes understanding of 'current session' (reasonable given sibling tools) but does not explain return value or error conditions. Acceptable for a simple recording tool.

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 covers both parameters with descriptions (100% coverage). Description supplements with examples for actionId (figma_verified, tests_passed), adding meaning beyond the schema's 'Verification action ID'. Metadata parameter is not further elaborated.

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?

Description clearly states the verb 'Record' and resource 'verification action in the current session' with concrete examples (figma_verified, tests_passed). It distinguishes from sibling tools like record_action_receipt by emphasizing session scope.

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?

Implies use for session-scoped verification actions with expiry, but does not explicitly state when not to use or compare to alternatives like record_action_receipt. No explicit guidance on prerequisites or context.

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

Deploy Server