cyclesite-mcp-server

suggest_listing_price

Read-onlyIdempotent

For a seller about to list: suggested ask, floor, and ceiling for their bike's brand+model[+year][+condition] on the UK market. Same measured UK used-price data as get_valuation but framed as seller guidance. Pass year when the seller names one — the ask is then anchored on that model year's own median rather than the all-years median. Example: 'I'm selling a 2021 Specialized Allez in good condition — what should I ask?'.

Input Schema

TableJSON Schema

Name	Required	Description
`year`	No	Model year, e.g. 2021. Optional. Anchors the ask on that year when the curve covers it; `basis` in the response always names what the ask was actually derived from.
`brand`	Yes
`model`	Yes
`condition`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 15, 2026

addedInput schema / properties / year

Added value: +{
+  "description": "Model year, e.g. 2021. Optional. Anchors the ask on that year when the curve covers it; `basis` in the response always names what the ask was actually derived from.",
+  "type": "number"
+}

First observedMay 7, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare readOnly, openWorld, and idempotent, so the bar for extra disclosure is lower. The description adds valuable behavioral context: the response contains ask/floor/ceiling, the `basis` field always names the derivation source, and year anchoring falls back to the all-years median when the curve doesn't cover that year. This goes well beyond the annotations.

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 purposeful sentences plus a compact example. The purpose and scope are front-loaded, the get_valuation distinction is one clause, and the example demonstrates realistic usage without 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?

With an output schema present, return-value documentation is unnecessary. The description covers the target user, data source, market scope, year-optional behavior, fallback behavior, and output fields (ask/floor/ceiling/basis). Nothing essential for an agent to invoke this correctly is missing.

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 only 25%, so the description must compensate. It does meaningfully explain the `year` parameter's optionality and anchoring behavior, and the example demonstrates condition usage. Brand and model remain lightly described, but their semantics are fairly self-evident and the schema marks them required.

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?

Description states a specific verb and resource: suggest ask/floor/ceiling for a seller's bike on the UK market. It explicitly differentiates from get_valuation by calling out the same data but seller-guidance framing, which clearly separates it from the nearest sibling.

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?

The description opens with 'For a seller about to list', establishing the target scenario, and explicitly contrasts with get_valuation. It also gives concrete conditional guidance: pass `year` when the seller names one, supported by a worked example.

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

All cyclesite-mcp-server 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.

Resources

Need Help?