Openpowerlifting

Opl Meet Results

opl_meet_results

Read-onlyIdempotent

Results of one powerlifting meet from the OpenPowerlifting database. Pass meet_id (from a previous call) or meet, a name search (every word must appear, e.g. "arnold classic"), optionally with federation (e.g. "USAPL", "IPF") and year to narrow it. If the search matches several meets the call returns the candidate list (meet_id, name, date, federation, town, country, entries) instead of guessing; with one match it returns the lifters ordered by sex, equipment, division, weight class and place, with bodyweight, best lifts, total, place and points. Optional filters sex (M/F/Mx), equipment, weight_class (e.g. "83", "84+") and division narrow the lifters. Rows page with limit/offset and report truncated/total_matching. No matching meet returns found:false with data_as_of. Weights are in kilograms.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "sex": "F",
      "limit": 5,
      "meet_id": 690,
      "weight_class": "63"
    },
    "name": "opl_meet_results"
  }
}

Input Schema

Name	Required	Description
`sex`	No
`meet`	No	Meet name search, e.g. "world classic".
`year`	No	Meet year.
`limit`	No	Lifters per page, 1-200 (default 50).
`offset`	No	Lifters to skip (default 0).
`meet_id`	No	Meet id from an earlier opl_meet_results / opl_lifter_history call.
`division`	No	Division text, e.g. "Open", "Juniors 20-23".
`equipment`	No
`federation`	No	Federation code, e.g. "IPF", "USAPL", "WRPF".
`weight_class`	No	Weight class as recorded, e.g. "83" or "84+".

Output Schema

Name	Required	Description	Default
`hint`	No
`meet`	No
`found`	No
`source`	No
`licence`	No
`results`	No
`returned`	No
`truncated`	No
`data_as_of`	No
`total_matching`	No
`latest_meet_date`	No
`copy_refreshed_at`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 26, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already cover safety and idempotency, but the description adds substantial behavioral context beyond them. It discloses that ambiguous searches return a candidate list instead of guessing, that one match returns ordered lifter rows, that paging reports truncation and totals, that no match returns found:false with data_as_of, and that weights are in kilograms.

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 description is dense but well front-loaded, starting with the resource and then covering lookup, return behavior, filters, pagination, and units. It could be split into clearer sentences for readability, but almost every clause carries useful information for a 10-parameter tool.

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?

Given the rich output schema and annotations, the description is complete enough to call correctly. It covers lookup inputs, ambiguity handling, filtering, pagination, no-match behavior, and units, leaving no important operational gap.

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 description coverage is high at 80%, so the schema already carries much of the parameter detail. The description still adds meaningful semantics: meet search requires every word to appear, federation and year narrow the meet search, sex/equipment/weight_class/division narrow lifter rows, and limit/offset page through results.

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?

The description states a specific verb/resource: results of one powerlifting meet from OpenPowerlifting. It distinguishes this from sibling tools by explaining meet lookup by meet_id or meet name and by describing the lifter-result output, so an agent can tell what it does without opening the 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?

It explicitly says to pass either meet_id or a meet name search, optionally narrowed by federation and year. It also explains the alternative behaviors for multi-match, single-match, and no-match cases, giving clear when-to-use guidance.

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

All Openpowerlifting tools Inspect

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.