Skip to main content
Glama
Sign In
Tennis Evolution

Tennis Evolution

by bobobo2026
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Activate a Pro licence key

activate_license

Verify a te1 license key offline and store it for future renders. This enables local tennis highlight reel processing without revalidation.

Instructions

Verify a te1.… key offline and store it for future renders.

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": {
      "key": "<key>"
    },
    "name": "activate_license"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full behavioral burden. It discloses offline verification and persistent storage, but omits key details such as what happens on failure, whether activation is idempotent, and what the tool returns.

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?

The description is a single, front-loaded sentence that communicates the core action and storage behavior without any filler. It is appropriately sized for a one-parameter tool.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations and no output schema, the description should cover more operational context. It is thin on failure modes, license status implications, and what the agent should expect after activation, leaving meaningful gaps for a licensing mutation.

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 0%, so the description must compensate for the single key parameter. It adds useful meaning by indicating the key format ('te1.…') and that it is verified offline, but it does not explain validation rules or error conditions.

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?

The description states a clear action: verify a key offline and store it for future renders. It identifies the resource as a 'te1.… key' and implies activation, though it does not explicitly differentiate from the sibling license_status tool.

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

Usage Guidelines2/5

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

The phrase 'for future renders' hints at when the tool is useful, but there is no explicit guidance on when to use it versus license_status or what prerequisites must be met. An agent must infer the usage context.

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

Deploy Server

Other Tools