TiresVote MCP

Official

by driveate

Overview Schema Source Related Servers Discussions Admin

Python

Remote

Evidence (reviews and professional tests)

tires_get_test

Read-onlyIdempotent

Fetch one professional tire test by slug, including participant scores, verdicts, and size availability; supports paging and optional size checks.

Instructions

Get one professional test with its participants.

test keeps the header (slug, title, link, year, season, automobile_type, tested tire_size, publication_date, regions) independent of participant paging. participants is a local slice: each entry keeps place, test_score (this test's own scale — never compare across tests), recommend, a bounded description verdict, positive_tags/negative_tags and the model identity (product with brand slug, canonical_link, rating and has_modes).

sizes_checked echoes the sizes argument. Results are valid for the tested size only; a participant having your requested size does not transfer the measurement to it. A cut verdict carries description_truncated and tags cap with positive_tags_more / negative_tags_more — the test's canonical_link is the full-report citation; per-size has_modes lists cap at 8 designations and tires_list_sizes holds the model's complete variant list. Responses cap at ~40 KB serialized — lower limit if a slice overflows.

Input Schema

TableJSON Schema

Name	Required	Description
`slug`	Yes	Test slug, e.g. '2027-adac-winter-tire-test-r17'. Resolve via tires_list_tests.
`limit`	No	Max participants per slice (1–50). Default 20.
`sizes`	No	Tire sizes to check on participants, each at most 30 chars (upstream bound), at most 20 sizes (an MCP-side bound), e.g. ['225/50R17']. Sent as repeated 'has_mode' params; each participant's product.has_modes then maps size → matched designations or null. This is an availability annotation — it does NOT change the tested size and does not guarantee every listed participant offers the size.
`offset`	No	Skip this many participants (0-based); follow next_offset.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 27, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare the safe read-only, idempotent, non-destructive profile, and the description adds substantial behavioral context: test_score must never be compared across tests, sizes_checked echoes the sizes argument without changing the tested size, cut verdicts carry description_truncated and tag overflow fields, canonical_link is the citation, and responses cap at ~40 KB serialized.

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 purpose is front-loaded in the first sentence, then dense but organized detail follows. Despite its length, nearly every sentence conveys a constraint or caveat that affects correct invocation or interpretation.

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 four parameters, 100% schema coverage, rich annotations, and an output schema, the description is more than complete enough. It covers paging behavior, size-check semantics, truncation, response limits, and sibling alternatives that an agent would otherwise have to infer.

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 100%, so the baseline is 3, but the description adds useful meaning beyond the schema: sizes is only an availability annotation that does not change the tested size, limit may need lowering if a slice overflows the ~40 KB response cap, offset should follow next_offset, and sizes_checked echoes the sizes argument.

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?

Starts with a specific verb and resource: 'Get one professional test with its participants.' It distinguishes the single-test resource from sibling list tools by naming tires_list_tests for slug resolution and tires_list_sizes for the complete variant list.

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

Usage Guidelines4/5

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

Provides clear context for when to use it: resolve the slug via tires_list_tests, and use tires_list_sizes when a complete model variant list is needed rather than the capped per-size has_modes list. It does not explicitly name when not to use this tool versus siblings like tires_get_pros_cons, but the routing guidance is otherwise clear.

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

Deploy Server