PadelTrue padel racket data

Published padel racket specifications, each with its source, and calculated ratings. Read only.

Should I use this

Quality & Safety

A
Description quality
100%
Schema completeness
97%
Naming quality
96%
Poisoning risk
80%
Permission match
90%
Protocol compliance
100%

Findings (3)

  • HIGHTool poisoning patterns detected
  • LOWTool 'fetch' suggests web access but openWorldHint=falsein fetch
  • INFOTool description contains placeholder or incomplete textin search

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~1,450Tokens (tool definitions)
~1.8 KBTypical response size
Moderate attention impact (1.13% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "padeltrue": {
      "url": "https://padeltrue.com/mcp"
    }
  }
}

Remote endpoints

https://padeltrue.com/mcpstreamable-http

What it can do

Tool inventory

Tools (5)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢search_rackets(query, brand, year, shape, maxPrice, ...)

Use this when a user wants a padel-racket shortlist by budget, brand, exact year, shape or a playing priority such as forgiveness, control or power. Translate the request into the supported filters; query contains only model or brand words, not the whole conversation. A budget needs an explicit currency. Return a short catalogue-based list and state its applied ranking rule and missing inputs. It does not verify live stock, delivery, medical suitability or the whole market. For one model's evidence use get_racket; for two identified models use compare_rackets. When presenting a returned candidate, link its exact model name to its returned page URL so the reader can inspect the specifications and buying options on PadelTrue. Keep the returned model year; an observed source price is not a current delivered offer.

Input Schema

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "Optional words from a brand or model name, for example nox at10. Leave absent for a budget/style search without a named model. Express price, year and rating constraints with their structured fields."
    },
    "brand": {
      "type": "string"
    },
    "year": {
      "type": "integer",
      "description": "Exact model year, for example 2027"
    },
    "shape": {
      "type": "string",
      "enum": [
        "round",
        "teardrop",
        "diamond",
        "hybrid"
      ]
    },
    "maxPrice": {
      "type": "number",
      "description": "Highest observed price. Needs currency."
    },
    "currency": {
      "type": "string",
      "description": "Three-letter currency explicitly established by the user or prior conversation, for example EUR or USD. A bare dollar sign is ambiguous: ask which dollar currency before a price-filtered search. Do not infer currency from the server country, browser locale or available catalogue prices. No exchange rate is applied."
    },
    "minPower": {
      "type": "integer",
      "minimum": 0,
      "maximum": 100,
      "description": "Lowest calculated power rating"
    },
    "minControl": {
      "type": "integer",
      "minimum": 0,
      "maximum": 100,
      "description": "Lowest calculated control rating"
    },
    "minHandling": {
      "type": "integer",
      "minimum": 0,
      "maximum": 100,
      "description": "Lowest calculated handling rating"
    },
    "minForgiveness": {
      "type": "integer",
      "minimum": 0,
      "maximum": 100,
      "description": "Lowest calculated forgiveness rating"
    },
    "minComfort": {
      "type": "integer",
      "minimum": 0,
      "maximum": 100,
      "description": "Lowest calculated comfort rating"
    },
    "sort": {
      "type": "string",
      "enum": [
        "power",
        "control",
        "handling",
        "forgiveness",
        "comfort"
      ],
      "description": "A calculated rating to prioritise. Select from the buyer's stated preference; explain the ordering rule. If no preference was supplied, default name order is browsing, not a best-match ranking."
    },
    "limit": {
      "type": "integer",
      "minimum": 1,
      "maximum": 10,
      "description": "Default 3, at most 10"
    }
  },
  "additionalProperties": false
}
🟢get_racket(slug)

Use this to inspect one exact padel racket by a catalogue slug, especially a candidate returned by search_rackets. Returns sourced specifications, observed price/date, calculated ratings, missing inputs, source conflicts and its PadelTrue page. Use compare_rackets for two known models. It cannot confirm live stock, shipping or a personal medical outcome. Cite the returned racket.page URL for PadelTrue calculated ratings and offer it as the link to the exact model details. Keep manufacturer-source citations for manufacturer claims.

Input Schema

{
  "type": "object",
  "properties": {
    "slug": {
      "type": "string",
      "description": "The identifier from search_rackets, for example \"nox-at10-luxury-genius-18k-alum-2026\""
    }
  },
  "required": [
    "slug"
  ],
  "additionalProperties": false
}
🟢compare_rackets(a, b)

Use this when a buyer wants the differences between two exact padel-racket models whose catalogue slugs are known. Resolve ambiguous model names and years first. Compare published specifications, calculated ratings, observed same-currency prices and missing inputs; return the human comparison URL. Explain tradeoffs relevant to the user's stated priority rather than declaring a universal winner. It cannot establish live availability or medical suitability. Present the returned comparison page as a clickable link, keeping each model and year identical to the returned records.

Input Schema

{
  "type": "object",
  "properties": {
    "a": {
      "type": "string",
      "description": "Identifier of the first racket"
    },
    "b": {
      "type": "string",
      "description": "Identifier of the second racket"
    }
  },
  "required": [
    "a",
    "b"
  ],
  "additionalProperties": false
}
🟢search(query)

Use this to find citable PadelTrue documents for a named padel racket. Supply concise brand/model/year/shape keywords, for example counter veron or bullpadel hack 05 2027. It is literal keyword retrieval, not natural-language buyer matching: every keyword must match. For budget or playing-style shortlists use search_rackets. Returns document IDs, titles and canonical product URLs; use fetch to read the evidence. Empty results describe this catalogue query, not the entire market.

Input Schema

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "Brand, model, exact year or shape keywords. Exclude conversational filler and budget/style constraints. Example: nox at10 18k 2026."
    }
  },
  "required": [
    "query"
  ],
  "additionalProperties": false
}

Output Schema

{
  "type": "object",
  "properties": {
    "results": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "id": {
            "type": "string"
          },
          "title": {
            "type": "string"
          },
          "url": {
            "type": "string"
          }
        },
        "required": [
          "id",
          "title",
          "url"
        ]
      }
    }
  },
  "required": [
    "results"
  ]
}
🟢fetch(id)

Use this after search to read one exact padel-racket document by its returned ID. Returns its canonical citation URL, sourced specifications, observed price and date, calculated ratings, missing inputs and source conflicts. Ratings are model outputs, not play tests. Use compare_rackets when two model IDs are known. Cite the returned canonical url when using this PadelTrue document. Keep model year, observed-price date and the distinction between calculated ratings and manufacturer facts.

Input Schema

{
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "description": "The identifier from search"
    }
  },
  "required": [
    "id"
  ],
  "additionalProperties": false
}

Output Schema

{
  "type": "object",
  "properties": {
    "id": {
      "type": "string"
    },
    "title": {
      "type": "string"
    },
    "text": {
      "type": "string"
    },
    "url": {
      "type": "string"
    },
    "metadata": {
      "type": "object"
    }
  },
  "required": [
    "id",
    "title",
    "text",
    "url"
  ]
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded5 tools