OpenPowerlifting MCP

Overview Schema Source Related Servers Discussions Admin

search_lifters

Read-onlyIdempotent

Find OpenPowerlifting lifters by name; all query words must match in any order, and suffixes like '#2' distinguish identical names. Results are sorted by number of meets.

Instructions

Find lifters by name. Every word must appear in the name, in any order.

A word like '#2' matches the OpenPowerlifting suffix used to tell apart lifters with the same name. Results are sorted by number of meets.

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": {
      "query": "<query>"
    },
    "name": "search_lifters"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`query`	Yes	Part of a name, e.g. 'ray williams' or 'doe #2'

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 6, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, closed-world), so the description's contribution is behavioral detail: AND-style token matching in any order, the '#2' OpenPowerlifting disambiguation suffix, and the fact that results are sorted by meet count. That sorting detail materially affects how an agent interprets result order, which annotations do not convey.

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?

Three short sentences, front-loaded with the action, each adding non-redundant information (matching rule, suffix rule, sort order). Nothing is repeated from the schema or padding.

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?

An output schema exists, so return-value detail is not needed, and the description still supplies the sort order that shapes interpretation of results. For a two-parameter read-only search tool, the remaining gap (limit semantics) is minor and already bounded by the schema.

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 50%: the query param has a description, but limit does not. The description compensates well for query, spelling out token-AND matching and the suffix convention that the schema example only hints at, though it says nothing about limit's default/max behavior beyond what the schema shows.

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 and resource ('Find lifters by name'), which is clearly distinct from siblings like lifter_history and compare_lifters. It does not explicitly name or contrast those siblings, so the distinction is inferable rather than stated.

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 description explains matching semantics but gives no guidance on when to choose this tool over lifter_history or compare_lifters, and no prerequisites or exclusions. An agent must infer that this is the lookup/entry point for all other lifter tools.

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

Deploy Server