Manufact

Back to submission

Lyon

lyon.weftd.space/mcp

Protocol: MCP 2025-11-25
Server version: 1.0.0
Supports: Tools
Resources
Prompts

Overall score

Last reviewed at Oct 14, 2026, 15:58:12 UTC

Server metadata

4 of 8 fields50/1004 / 8 pts

Identity, discovery, and usage metadata advertised during the MCP handshake.

Stable server name

Lyon

10/10Source

Human-readable title

Add a human-readable title for clients and directories.

0/10Source

Useful description

Describe what the server helps an agent do.

0/20Source

Server version

Version 1.0.0

10/10Source

Public website

Link to a public website or documentation page.

0/10Source

Scalable or high-resolution icon

Advertise a vector or at least 128px server icon.

0/10Source

Server instructions

Usage instructions provided for agents.

20/20Source

Declared capabilities

Supports Tools, Resources, Prompts.

10/10Source

Extensions

io.modelcontextprotocol/skillsio.modelcontextprotocol/ui

Server instructions

--- name: lyon-guide description: Use this skill when a user asks for recommendations or information about Lyon, France. This includes local attractions, food, activities, and navigation within the city. --- This MCP server provides a comprehensive knowledge base and tools for acting as a local guide for Lyon, France. It allows for searching local content, displaying map information, and accessing real-time transportation and parking data. ## Tools * **search_lyon_content**: Use this tool to find information about Lyon, such as restaurant recommendations, historical sites, activities, and local tips. It returns text-based information. * **search_media**: Use this tool to find images related to Lyon when a visual representation would enhance a recommendation (e.g., a specific landmark or dish). * **list_entries**: Use this tool to discover the types of content available within the Lyon knowledge base. * **get_weather**: Use this tool when recommending outdoor activities or providing daily plans to ensure the suggestion is weather-appropriate. * **get_time**: Use this tool to provide the current time in Lyon. * **display_map**: Use this tool to show the location of recommended places, routes, or to answer "where is" questions. It returns a map visualization. * **show_metro_line_diagram**: Use this tool to display metro line diagrams, aiding in real-time navigation and planning when a user asks about metro routes or services. * **get_parking**: Use this to retrieve detailed information about a specific parking lot when the user names it. * **search_parkings**: Use this to find available parking lots near a specified location in Lyon. ## Example User: "What's a good place for dinner in Lyon tonight?" Agent: Calls `search_lyon_content` with query "best dinner restaurants Lyon". Agent receives a recommendation for 'Le Jardin des Saveurs', including its address, price range, and signature dishes. Agent then calls `search_media` with query "Le Jardin de

Protocol

Pass100/10016 / 16 pts

Connection, authentication, and protocol compatibility.

MCP negotiation succeeds (v1/v2)

MCP legacy negotiation succeeded in 2487ms

Source

Tools list returns results

13 tool(s) returned

Source

Resources list responds

6 resource(s) returned

Source

Server declares tools capability

Server declares tools capability in initialize response

Source

Tools

Issues89/10021.4 / 24 pts

Tool definitions, annotations, and client compatibility.

All tools have descriptions

All tools have non-empty descriptions

Claude Code metadata fits its 2 KB fields

1 metadata field(s) exceed Claude Code's 2 KB truncation point

How to fix: Keep each tool description and the server instructions field at or below 2 KB, and put critical guidance first.

warningclaude-code

Source

All tools have OpenAI behavior hints

8 behavior annotation issue(s) found

How to fix: On each tool, declare annotations.readOnlyHint, annotations.destructiveHint, and annotations.openWorldHint as booleans. The policy review separately assesses whether their values match the tool's actual behavior.

errorChatGPT

Source

Skills over MCP resources are readable

Validated 1 skill(s) and 1 resource(s) across 1 catalog page(s)

Claude tools declare applicable behavior hints

All tools include an applicable readOnlyHint or destructiveHint

Source

Claude tool names are within 64 characters

All tool names are within Claude's 64-character limit

Source

Tool names use valid characters

All tool names use valid characters

Source

All tools have a display title

Source

Tool input schemas have a valid object structure

All tool input schemas have a valid object structure

Source

OpenAI file parameters use valid schemas

All declared OpenAI file parameters use reviewer-valid schemas

Source

Tool names follow the MCP 1–128 character range

All tool names follow the MCP recommended length

Source

Tool names follow MCP uniqueness guidance

All tool names are unique

Source

ChatGPT tool names are unique

All tool names are unique

Source

Cursor tool-name budget advisory

No tool name independently exhausts Cursor's observed 60-character combined budget

Observed behavior

Tool input header annotations are valid

All x-mcp-header annotations satisfy Streamable HTTP requirements

Source

Declared output schemas have a valid basic structure

0 declared output schema(s) pass basic structural validation; schemas may describe any JSON value, including arrays

Source

Tool text has no hidden control characters

No invisible or control characters found in tool-facing text

Source

MCP Apps

Issues68/10013.6 / 20 pts

App resources, metadata, and rendering requirements.

All discovered view resources were inspected

Inspected all 5 discovered view resource(s)

Source

View resource envelope is valid

All view resources are readable and use ui:// with a supported MCP Apps HTML MIME type

Tool invocation metadata present

All view-linked tools have invoking/invoked metadata

Source

Tool-linked resource URI is readable

All tool-linked resource URIs are readable

Source

Tool visibility metadata is valid

All explicit ui.visibility arrays are valid

Source

CSP metadata covers literal external origins

All statically detectable external origins are declared in CSP metadata

Source

View resource metadata complete

5 resource(s) have incomplete metadata

How to fix: Use a ui:// URI and text/html;profile=mcp-app. For mcp-use v1, use widgetMetadata.metadata.widgetDescription; for v2, use the bound tool's view.description. The current description check reads _meta.ui.widgetDescription or _meta["openai/widgetDescription"] on resource contents or linked tools, not resource.description. Consequently, v2 view.description alone may leave this warning: report the checker compatibility gap instead of adding unsupported v1 fields or claiming the warning is fixed.

warningChatGPTClaude.ai

Source

View resources declare a domain

1 ChatGPT UI domain issue(s) found

How to fix: For ChatGPT submission, set one exact HTTPS origin such as "https://app.example.com" on every view via _meta.ui.domain (or openai/widgetDomain). Paths are not valid and all views in one app must share the origin.

errorChatGPT

Source

Declared domains respond

1 domain(s) not responding

warningChatGPTClaude.ai

Tool documentation quality

13 tools reviewed67/10021.4 / 32 pts

How clearly each tool’s title, description, input and output schemas, and behavior annotations guide an agent.

get_metro_lineTitles 100Descriptions 87Inputs 75Annotations 50Outputs 075/100

Title100/100

Get Metro Line

The title clearly communicates the tool’s action and subject. Keep it concise.

Description87/100

Return the full station list for a Lyon metro or funicular line ordered geographically, with next real-time departure per direction for each station.

The description explains the capability, when to use it, and what to expect.

Inputs75/100

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

lineId

Metro line code: 'A', 'B', 'D', 'F1', 'F2'

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

Annotations50/100

Declare destructiveHint, idempotentHint based on the tool’s actual behavior.

{
  "title": "Get Metro Line",
  "readOnlyHint": true,
  "openWorldHint": true
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get_metro_line",
  "description": "Return the full station list for a Lyon metro or funicular line ordered geographically, with next real-time departure per direction for each station.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "lineId"
    ],
    "properties": {
      "lineId": {
        "type": "string",
        "description": "Metro line code: 'A', 'B', 'D', 'F1', 'F2'"
      }
    }
  },
  "annotations": {
    "title": "Get Metro Line",
    "readOnlyHint": true,
    "openWorldHint": true
  }
}

show_parking_spotTitles 99Descriptions 76Inputs 48Annotations 50Outputs 064/100

Title99/100

Show Parking Spot

The title clearly communicates the tool’s action and subject. Keep it concise.

Description76/100

Display a parking lot's live availability, pricing, EV charging spots, height limit, and amenities in Lyon.

The description explains the capability, when to use it, and what to expect.

Inputs48/100

8 of 12 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

ev › total

Not provided

Missing description. Explain what this value means and how to supply it.

ev › available

Not provided

Missing description. Explain what this value means and how to supply it.

name

Parking name

Clear enough to supply this argument.

price

Price string, e.g. '€3.80'

Clarify units, where to obtain this value, or conventions not already expressed in the schema.

total

Total capacity

Clear enough to supply this argument.

height

Max vehicle height, e.g. '1.90m'

Clarify units, where to obtain this value, or conventions not already expressed in the schema.

address

Full address

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

distance

Distance from user, e.g. '240m'

Clear enough to supply this argument.

services

Not provided

Missing description. Explain what this value means and how to supply it.

available

Available spaces right now

Clarify units, where to obtain this value, or conventions not already expressed in the schema.

openHours

Opening hours, e.g. '24/7'

Clarify units, where to obtain this value, or conventions not already expressed in the schema.

priceUnit

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations50/100

Declare destructiveHint, idempotentHint based on the tool’s actual behavior.

{
  "title": "Show Parking Spot",
  "readOnlyHint": true,
  "openWorldHint": true
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "show_parking_spot",
  "description": "Display a parking lot's live availability, pricing, EV charging spots, height limit, and amenities in Lyon.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "ev",
      "name",
      "price",
      "total",
      "address",
      "available"
    ],
    "properties": {
      "ev": {
        "type": "object",
        "required": [
          "total",
          "available"
        ],
        "properties": {
          "total": {
            "type": "integer",
            "maximum": 9007199254740991,
            "minimum": -9007199254740991
          },
          "available": {
            "type": "integer",
            "maximum": 9007199254740991,
            "minimum": -9007199254740991
          }
        },
        "description": "EV charging spots"
      },
      "name": {
        "type": "string",
        "description": "Parking name"
      },
      "price": {
        "type": "string",
        "description": "Price string, e.g. '€3.80'"
      },
      "total": {
        "type": "integer",
        "maximum": 9007199254740991,
        "minimum": -9007199254740991,
        "description": "Total capacity"
      },
      "height": {
        "type": "string",
        "description": "Max vehicle height, e.g. '1.90m'"
      },
      "address": {
        "type": "string",
        "description": "Full address"
      },
      "distance": {
        "type": "string",
        "description": "Distance from user, e.g. '240m'"
      },
      "services": {
        "type": "array",
        "items": {
          "enum": [
            "covered",
            "cctv",
            "ev",
            "accessible",
            "24h"
          ],
          "type": "string"
        }
      },
      "available": {
        "type": "integer",
        "maximum": 9007199254740991,
        "minimum": -9007199254740991,
        "description": "Available spaces right now"
      },
      "openHours": {
        "type": "string",
        "description": "Opening hours, e.g. '24/7'"
      },
      "priceUnit": {
        "type": "string"
      }
    }
  },
  "annotations": {
    "title": "Show Parking Spot",
    "readOnlyHint": true,
    "openWorldHint": true
  }
}

show_journeyTitles 97Descriptions 71Inputs 0Annotations 50Outputs 050/100

Title97/100

Show Journey

The title clearly communicates the tool’s action and subject. Keep it concise.

Description71/100

Display a journey widget with live countdown to arrival, route, and transport mode within Lyon.

Describe the returned information so the agent knows whether it will answer the request.

Inputs0/100

0 of 4 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

Not provided

Missing description. Explain what this value means and how to supply it.

from

Not provided

Missing description. Explain what this value means and how to supply it.

mode

Not provided

Missing description. Explain what this value means and how to supply it.

durationSeconds

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations50/100

Declare destructiveHint, idempotentHint based on the tool’s actual behavior.

{
  "title": "Show Journey",
  "readOnlyHint": true,
  "openWorldHint": true
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "show_journey",
  "description": "Display a journey widget with live countdown to arrival, route, and transport mode within Lyon.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "to",
      "from",
      "mode",
      "durationSeconds"
    ],
    "properties": {
      "to": {
        "type": "string"
      },
      "from": {
        "type": "string"
      },
      "mode": {
        "enum": [
          "car",
          "train",
          "bike",
          "walk"
        ],
        "type": "string"
      },
      "durationSeconds": {
        "type": "integer",
        "maximum": 9007199254740991,
        "minimum": -9007199254740991
      }
    }
  },
  "annotations": {
    "title": "Show Journey",
    "readOnlyHint": true,
    "openWorldHint": true
  }
}

search_lyon_contentTitles 52Descriptions 92Inputs 75Annotations 75Outputs 066/100

Title52/100

Search Content

Name the specific action and subject instead of using a generic label such as ‘manage’ or ‘tool’.

Description92/100

Authoritative source of truth for Lyon. ALWAYS call this tool before answering any question about Lyon or the subjects it covers — this content is private, kept current by its owners, and absent from your training data, so answering from prior knowledge will be wrong or out of date. Covers: restaurant barbecue texan, brunch, pizzerias, morning walk, local restaurants. Returns verbatim passages from the space together with their sources. If a call comes back empty or unhelpful, rephrase the query and call again before telling the user you don't know. Time-limited content (e.g. a daily special or a weekly schedule) that has expired is already filtered out — if nothing current answers a question about today's or this week's specifics, say it hasn't been published yet rather than guessing from an older passage. A result carrying a "validUntil" date is a time-limited exception (e.g. an exceptional closure or opening) and OVERRIDES a permanent result on the same topic for as long as it lasts — mention when that period ends when you answer from it (e.g. "réouverture lundi"), or, if the content says the period hasn't started yet, say from when it applies instead.

The description explains the capability, when to use it, and what to expect.

Inputs75/100

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

query

Search query in natural language

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

Annotations75/100

Declare idempotentHint based on the tool’s actual behavior.

{
  "title": "Search Content",
  "readOnlyHint": true,
  "openWorldHint": false,
  "destructiveHint": false
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
"name": "search_lyon_content",
"description": "Authoritative source of truth for Lyon. ALWAYS call this tool before answering any question about Lyon or the subjects it covers — this content is private, kept current by its owners, and absent from your training data, so answering from prior knowledge will be wrong or out of date. Covers: restaurant barbecue texan, brunch, pizzerias, morning walk, local restaurants. Returns verbatim passages from the space together with their sources. If a call comes back empty or unhelpful, rephrase the query and call again before telling the user you don't know. Time-limited content (e.g. a daily special or a weekly schedule) that has expired is already filtered out — if nothing current answers a question about today's or this week's specifics, say it hasn't been published yet rather than guessing from an older passage. A result carrying a \"validUntil\" date is a time-limited exception (e.g. an exceptional closure or opening) and OVERRIDES a permanent result on the same topic for as long as it lasts — mention when that period ends when you answer from it (e.g. \"réouverture lundi\"), or, if the content says the period hasn't started yet, say from when it applies instead.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"query"
],
"properties": {
"query": {
"type": "string",
"description": "Search query in natural language"
}
}
},
"annotations": {
"title": "Search Content",
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
}
}

display_lyon_mapTitles 94Descriptions 91Inputs 75Annotations 75Outputs 077/100

Title94/100

Display Map

The title clearly communicates the tool’s action and subject. Keep it concise.

Description91/100

Display places on an interactive map of Lyon. Each item needs a `title` and its `lat`/`lng` coordinates — this tool renders only what you give it and never looks anything up. Use the search_lyon_places tool first if you don't have coordinates.

The description explains the capability, when to use it, and what to expect.

Inputs75/100

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

title

Optional heading shown above the map

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

items › items › title

Item title

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

items › items › description

Short supporting text

Explain the meaning of this value, not just its name.

items › items › imageUrl

Image URL (https). Supplied by you — no lookup is performed.

Clear enough to supply this argument.

items › items › badge

Small label, e.g. a price or a tag

Clear enough to supply this argument.

items › items › action › label

Button label

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

items › items › action › prompt

Follow-up message sent to the assistant when clicked

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

items › items › lat

Latitude

Clarify units, where to obtain this value, or conventions not already expressed in the schema.

items › items › lng

Longitude

Clarify units, where to obtain this value, or conventions not already expressed in the schema.

items › items › location

Full address or location description

Clear enough to supply this argument.

items › items › rating

Rating if available

Clarify units, where to obtain this value, or conventions not already expressed in the schema.

items › items › tags

Tags or categories

Clear enough to supply this argument.

Annotations75/100

Declare idempotentHint based on the tool’s actual behavior.

{
  "title": "Display Map",
  "readOnlyHint": true,
  "openWorldHint": false,
  "destructiveHint": false
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "display_lyon_map",
  "description": "Display places on an interactive map of Lyon. Each item needs a `title` and its `lat`/`lng` coordinates — this tool renders only what you give it and never looks anything up. Use the search_lyon_places tool first if you don't have coordinates.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "items"
    ],
    "properties": {
      "items": {
        "type": "array",
        "items": {
          "type": "object",
          "required": [
            "lat",
            "lng"
          ],
          "properties": {
            "lat": {
              "type": "number",
              "description": "Latitude"
            },
            "lng": {
              "type": "number",
              "description": "Longitude"
            },
            "tags": {
              "type": "array",
              "items": {
                "type": "string"
              },
              "description": "Tags or categories"
            },
            "badge": {
              "type": "string",
              "description": "Small label, e.g. a price or a tag"
            },
            "title": {
              "type": "string",
              "description": "Item title"
            },
            "action": {
              "type": "object",
              "required": [
                "label",
                "prompt"
              ],
              "properties": {
                "label": {
                  "type": "string",
                  "description": "Button label"
                },
                "prompt": {
                  "type": "string",
                  "description": "Follow-up message sent to the assistant when clicked"
                }
              },
              "description": "Optional call-to-action"
            },
            "rating": {
              "type": "number",
              "description": "Rating if available"
            },
            "imageUrl": {
              "type": "string",
              "description": "Image URL (https). Supplied by you — no lookup is performed."
            },
            "location": {
              "type": "string",
              "description": "Full address or location description"
            },
            "description": {
              "type": "string",
              "description": "Short supporting text"
            }
          }
        },
        "description": "Places to display on the map. `title`, `lat` and `lng` are required on each item."
      },
      "title": {
        "type": "string",
        "description": "Optional heading shown above the map"
      }
    }
  },
  "annotations": {
    "title": "Display Map",
    "readOnlyHint": true,
    "openWorldHint": false,
    "destructiveHint": false
  }
}

get_lyon_weatherTitles 89Descriptions 80Inputs 96Annotations 75Outputs 078/100

Title89/100

Get Weather

The title clearly communicates the tool’s action and subject. Keep it concise.

Description80/100

Display current weather conditions including temperature, humidity, wind, and precipitation forecast for Lyon.

Describe the returned information so the agent knows whether it will answer the request.

Inputs96/100

Input documentation gives an agent enough context to populate the arguments.

location

City name, optionally with country code (e.g. 'Lyon, FR', 'Paris')

Clear enough to supply this argument.

Annotations75/100

Declare idempotentHint based on the tool’s actual behavior.

{
  "title": "Get Weather",
  "readOnlyHint": true,
  "openWorldHint": true,
  "destructiveHint": false
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get_lyon_weather",
  "description": "Display current weather conditions including temperature, humidity, wind, and precipitation forecast for Lyon.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "location"
    ],
    "properties": {
      "location": {
        "type": "string",
        "description": "City name, optionally with country code (e.g. 'Lyon, FR', 'Paris')"
      }
    }
  },
  "annotations": {
    "title": "Get Weather",
    "readOnlyHint": true,
    "openWorldHint": true,
    "destructiveHint": false
  }
}

show_metro_lineTitles 99Descriptions 79Inputs 50Annotations 50Outputs 066/100

Title99/100

Show Metro Line

The title clearly communicates the tool’s action and subject. Keep it concise.

Description79/100

Display a metro/subway line diagram for Lyon with current station, upcoming stations, transfer connections, and next train arrivals.

The description explains the capability, when to use it, and what to expect.

Inputs50/100

6 of 10 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

line

Line number/letter, e.g. '14'

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

lineName

Full name, e.g. 'Métro 14'

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

stations › items › name

Not provided

Missing description. Explain what this value means and how to supply it.

stations › items › passed

Not provided

Missing description. Explain what this value means and how to supply it.

stations › items › current

Not provided

Missing description. Explain what this value means and how to supply it.

stations › items › transfer

Not provided

Missing description. Explain what this value means and how to supply it.

direction

Direction/terminus, e.g. 'Olympiades'

Clear enough to supply this argument.

lineColor

Line color hex

Clear enough to supply this argument.

nextArrivals

Minutes until next trains [3, 7, 12]

Clarify units, where to obtain this value, or conventions not already expressed in the schema.

currentStation

Station where user currently is

Clear enough to supply this argument.

Annotations50/100

Declare destructiveHint, idempotentHint based on the tool’s actual behavior.

{
  "title": "Show Metro Line",
  "readOnlyHint": true,
  "openWorldHint": true
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "show_metro_line",
  "description": "Display a metro/subway line diagram for Lyon with current station, upcoming stations, transfer connections, and next train arrivals.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "line",
      "lineName",
      "stations",
      "direction",
      "lineColor",
      "nextArrivals",
      "currentStation"
    ],
    "properties": {
      "line": {
        "type": "string",
        "description": "Line number/letter, e.g. '14'"
      },
      "lineName": {
        "type": "string",
        "description": "Full name, e.g. 'Métro 14'"
      },
      "stations": {
        "type": "array",
        "items": {
          "type": "object",
          "required": [
            "name",
            "passed",
            "current"
          ],
          "properties": {
            "name": {
              "type": "string"
            },
            "passed": {
              "type": "boolean"
            },
            "current": {
              "type": "boolean"
            },
            "transfer": {
              "type": "array",
              "items": {
                "type": "string"
              }
            }
          }
        },
        "description": "All stations on the line in order"
      },
      "direction": {
        "type": "string",
        "description": "Direction/terminus, e.g. 'Olympiades'"
      },
      "lineColor": {
        "type": "string",
        "description": "Line color hex"
      },
      "nextArrivals": {
        "type": "array",
        "items": {
          "type": "integer",
          "maximum": 9007199254740991,
          "minimum": -9007199254740991
        },
        "description": "Minutes until next trains [3, 7, 12]"
      },
      "currentStation": {
        "type": "string",
        "description": "Station where user currently is"
      }
    }
  },
  "annotations": {
    "title": "Show Metro Line",
    "readOnlyHint": true,
    "openWorldHint": true
  }
}

get_parking_lotTitles 91Descriptions 95Inputs 96Annotations 50Outputs 080/100

Title91/100

Get Parking

The title clearly communicates the tool’s action and subject. Keep it concise.

Description95/100

Find a single parking lot in Lyon by name using fuzzy matching. Returns full real-time record with availability and pricing.

The description explains the capability, when to use it, and what to expect.

Inputs96/100

Input documentation gives an agent enough context to populate the arguments.

name

Parking name, exact or approximate: 'Terreaux', 'LPA Terreaux', 'terreaux'

Clear enough to supply this argument.

Annotations50/100

Declare destructiveHint, idempotentHint based on the tool’s actual behavior.

{
  "title": "Get Parking",
  "readOnlyHint": true,
  "openWorldHint": true
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get_parking_lot",
  "description": "Find a single parking lot in Lyon by name using fuzzy matching. Returns full real-time record with availability and pricing.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "name"
    ],
    "properties": {
      "name": {
        "type": "string",
        "description": "Parking name, exact or approximate: 'Terreaux', 'LPA Terreaux', 'terreaux'"
      }
    }
  },
  "annotations": {
    "title": "Get Parking",
    "readOnlyHint": true,
    "openWorldHint": true
  }
}

search_parkingsTitles 100Descriptions 91Inputs 88Annotations 50Outputs 079/100

Title100/100

Search Parkings

The title clearly communicates the tool’s action and subject. Keep it concise.

Description91/100

Geocode a free-text destination (address, POI, neighbourhood) in Lyon and return all open parking lots within a radius, sorted by distance, with real-time availability.

The description explains the capability, when to use it, and what to expect.

Inputs88/100

Explain what happens when this optional value is omitted.

radius_m

Search radius in metres (default: 800)

Clear enough to supply this argument.

destination

Free text: 'Opéra de Lyon', 'Bellecour', '69001'…

Clear enough to supply this argument.

min_available

Only return lots with at least N available spaces

Explain what happens when this optional value is omitted.

Annotations50/100

Declare destructiveHint, idempotentHint based on the tool’s actual behavior.

{
  "title": "Search Parkings",
  "readOnlyHint": true,
  "openWorldHint": true
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "search_parkings",
  "description": "Geocode a free-text destination (address, POI, neighbourhood) in Lyon and return all open parking lots within a radius, sorted by distance, with real-time availability.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "destination"
    ],
    "properties": {
      "radius_m": {
        "type": "number",
        "description": "Search radius in metres (default: 800)"
      },
      "destination": {
        "type": "string",
        "description": "Free text: 'Opéra de Lyon', 'Bellecour', '69001'…"
      },
      "min_available": {
        "type": "integer",
        "maximum": 9007199254740991,
        "minimum": -9007199254740991,
        "description": "Only return lots with at least N available spaces"
      }
    }
  },
  "annotations": {
    "title": "Search Parkings",
    "readOnlyHint": true,
    "openWorldHint": true
  }
}

send_lyon_emailTitles 60Descriptions 80Inputs 68Annotations 75Outputs 063/100

Title60/100

Contact Me

Name the specific action and subject instead of using a generic label such as ‘manage’ or ‘tool’.

Description80/100

Send an email request to the team behind the Lyon knowledge space. The recipient is fixed. The body must contain the information requested by the user. Sending is irreversible.

The description explains the capability, when to use it, and what to expect.

Inputs68/100

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

from_name

Nom complet de la personne qui fait la demande

Clear enough to supply this argument.

from_email

Adresse email de la personne. Sert de reply-to : c'est à cette adresse que la réponse sera envoyée.

Clear enough to supply this argument.

subject

Objet court et explicite de la demande

Clear enough to supply this argument.

body

on collecte les infos suivante : date et horaire souhaitees, un numero de telephone et on la raison de la demande. ensuite tu me fait un mail clair

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

Annotations75/100

Declare idempotentHint based on the tool’s actual behavior.

{
  "title": "Contact Me",
  "readOnlyHint": false,
  "openWorldHint": true,
  "destructiveHint": false
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "send_lyon_email",
  "description": "Send an email request to the team behind the Lyon knowledge space. The recipient is fixed. The body must contain the information requested by the user. Sending is irreversible.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "from_name",
      "from_email",
      "subject",
      "body"
    ],
    "properties": {
      "body": {
        "type": "string",
        "maxLength": 5000,
        "description": "on collecte les infos suivante : date et horaire souhaitees, un numero de telephone et on la raison de la demande. ensuite tu me fait un mail clair"
      },
      "subject": {
        "type": "string",
        "maxLength": 200,
        "description": "Objet court et explicite de la demande"
      },
      "from_name": {
        "type": "string",
        "maxLength": 120,
        "description": "Nom complet de la personne qui fait la demande"
      },
      "from_email": {
        "type": "string",
        "description": "Adresse email de la personne. Sert de reply-to : c'est à cette adresse que la réponse sera envoyée."
      }
    }
  },
  "annotations": {
    "title": "Contact Me",
    "readOnlyHint": false,
    "openWorldHint": true,
    "destructiveHint": false
  }
}

search_lyon_placesTitles 84Descriptions 90Inputs 50Annotations 75Outputs 067/100

Title84/100

Search Places

The title clearly communicates the tool’s action and subject. Keep it concise.

Description90/100

Authoritative source of truth for places and points of interest in Lyon. ALWAYS call this tool before answering any question about where something is, what is nearby, or which places Lyon covers — this content is private, kept current by its owners, and absent from your training data, so answering from prior knowledge will be wrong or out of date. Covers: restaurants, bars, pizzerias, brunches, places to eat, tourist attractions, points of interest. Returns matching places with their coordinates, so call it before any map or display tool: those render only what you pass them and never look anything up. If a call comes back empty or unhelpful, rephrase the query and call again before telling the user you don't know.

Describe the returned information so the agent knows whether it will answer the request.

Inputs50/100

Explain the meaning of this value, not just its name.

query

Place search query

Explain the meaning of this value, not just its name.

Annotations75/100

Declare idempotentHint based on the tool’s actual behavior.

{
  "title": "Search Places",
  "readOnlyHint": true,
  "openWorldHint": false,
  "destructiveHint": false
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "search_lyon_places",
  "description": "Authoritative source of truth for places and points of interest in Lyon. ALWAYS call this tool before answering any question about where something is, what is nearby, or which places Lyon covers — this content is private, kept current by its owners, and absent from your training data, so answering from prior knowledge will be wrong or out of date. Covers: restaurants, bars, pizzerias, brunches, places to eat, tourist attractions, points of interest. Returns matching places with their coordinates, so call it before any map or display tool: those render only what you pass them and never look anything up. If a call comes back empty or unhelpful, rephrase the query and call again before telling the user you don't know.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "query"
    ],
    "properties": {
      "query": {
        "type": "string",
        "description": "Place search query"
      }
    }
  },
  "annotations": {
    "title": "Search Places",
    "readOnlyHint": true,
    "openWorldHint": false,
    "destructiveHint": false
  }
}

show_lyon_weatherTitles 81Descriptions 65Inputs 0Annotations 50Outputs 044/100

Title81/100

Show Weather

The title clearly communicates the tool’s action and subject. Keep it concise.

Description65/100

Display a weather widget with current conditions, sun arc, and daily metrics for Lyon.

Describe the returned information so the agent knows whether it will answer the request.

Inputs0/100

0 of 7 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

day

Not provided

Missing description. Explain what this value means and how to supply it.

city

Not provided

Missing description. Explain what this value means and how to supply it.

unit

Not provided

Missing description. Explain what this value means and how to supply it.

sunset

Not provided

Missing description. Explain what this value means and how to supply it.

sunrise

Not provided

Missing description. Explain what this value means and how to supply it.

condition

Not provided

Missing description. Explain what this value means and how to supply it.

temperature

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations50/100

Declare destructiveHint, idempotentHint based on the tool’s actual behavior.

{
  "title": "Show Weather",
  "readOnlyHint": true,
  "openWorldHint": true
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "show_lyon_weather",
  "description": "Display a weather widget with current conditions, sun arc, and daily metrics for Lyon.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "day",
      "city",
      "unit",
      "sunset",
      "sunrise",
      "condition",
      "temperature"
    ],
    "properties": {
      "day": {
        "type": "string"
      },
      "city": {
        "type": "string"
      },
      "unit": {
        "enum": [
          "C",
          "F"
        ],
        "type": "string"
      },
      "sunset": {
        "type": "string"
      },
      "sunrise": {
        "type": "string"
      },
      "condition": {
        "enum": [
          "sunny",
          "rainy",
          "cloudy",
          "snowy",
          "stormy",
          "windy"
        ],
        "type": "string"
      },
      "temperature": {
        "type": "number"
      }
    }
  },
  "annotations": {
    "title": "Show Weather",
    "readOnlyHint": true,
    "openWorldHint": true
  }
}

search_lyon_newsTitles 95Descriptions 48Inputs 95Annotations 50Outputs 068/100

Title95/100

Search News

The title clearly communicates the tool’s action and subject. Keep it concise.

Description48/100

Make a search on news, on the subject of your choice.

Describe the concrete operation and its scope instead of restating the tool name.

Inputs95/100

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

Country code for news region (ISO 3166-1 alpha-2). Determines which country's news sources to prioritize.

Clear enough to supply this argument.

Language code for news interface and results. Most languages use ISO 639-1 codes (e.g., 'en', 'es'). Chinese requires regional variants: 'zh-cn' (Simplified) or 'zh-tw' (Traditional). Standalone 'zh' is normalized to 'zh-cn'.

Clear enough to supply this argument.

when

Time filter for news articles. 'd' = past day, 'w' = past week, 'm' = past month, 'y' = past year. These are coarse UTC-based buckets with no finer granularity; filter `published_at` client-side for precise ranges. Combining narrow queries with strict `when` filters frequently returns zero results; broaden either before concluding no data exists.

Clear enough to supply this argument.

query

Search query for news articles. Supports advanced operators like 'site:', 'when:', etc. Cannot be used with topic_token, publication_token, or story_token.

Clear enough to supply this argument.

start

Result offset for pagination. Each page typically contains 10 results. Use multiples of 10 (0, 10, 20, 30, ...) to navigate pages. Stop paginating when a page returns no new results.

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

Annotations50/100

Declare destructiveHint, idempotentHint based on the tool’s actual behavior.

{
  "title": "Search News",
  "readOnlyHint": true,
  "openWorldHint": true
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "search_lyon_news",
  "description": "Make a search on news, on the subject of your choice.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {
      "gl": {
        "type": "string",
        "description": "Country code for news region (ISO 3166-1 alpha-2). Determines which country's news sources to prioritize."
      },
      "hl": {
        "type": "string",
        "description": "Language code for news interface and results. Most languages use ISO 639-1 codes (e.g., 'en', 'es'). Chinese requires regional variants: 'zh-cn' (Simplified) or 'zh-tw' (Traditional). Standalone 'zh' is normalized to 'zh-cn'."
      },
      "when": {
        "type": "string",
        "description": "Time filter for news articles. 'd' = past day, 'w' = past week, 'm' = past month, 'y' = past year. These are coarse UTC-based buckets with no finer granularity; filter `published_at` client-side for precise ranges. Combining narrow queries with strict `when` filters frequently returns zero results; broaden either before concluding no data exists."
      },
      "query": {
        "type": "string",
        "description": "Search query for news articles. Supports advanced operators like 'site:', 'when:', etc. Cannot be used with topic_token, publication_token, or story_token."
      },
      "start": {
        "type": "integer",
        "maximum": 9007199254740991,
        "minimum": -9007199254740991,
        "description": "Result offset for pagination. Each page typically contains 10 results. Use multiples of 10 (0, 10, 20, 30, ...) to navigate pages. Stop paginating when a page returns no new results."
      }
    }
  },
  "annotations": {
    "title": "Search News",
    "readOnlyHint": true,
    "openWorldHint": true
  }
}

Put your MCP to the test

A few tasks worth trying with this server, chosen from its reviewed tools. These have not been run.

01Get WeatherDisplay current weather conditions including temperature, humidity, wind, and precipitation forecast for Lyon.
02Search PlacesAuthoritative source of truth for places and points of interest in Lyon.
03Search ParkingsGeocode a free-text destination (address, POI, neighbourhood) in Lyon and return all open parking lots within a radius, sorted by distance, with real-time av…
04Get parking lotFind a single parking lot in Lyon by name using fuzzy matching.
05Search NewsMake a search on news, on the subject of your choice.

Want to run these tasks against your MCP server with us?

Test your MCP in Cloud Book a test call

FAQ

Lyon setup, tools, quality score, publishing readiness, and alternatives.

How do I add Lyon to Claude, ChatGPT, or Cursor?

Add Lyon to Claude, ChatGPT, or Cursor by connecting its remote MCP URL in each client's MCP settings. In Claude, add a custom connector. In ChatGPT, add an MCP app. In Cursor, add an MCP server under Settings. The MCP URL is https://lyon.weftd.space/mcp.

Is Lyon MCP ready for ChatGPT and Claude?

As of October 14, 2026, Lyon scores 84/100 on Manufact's MCP publishing checklist. The scan does not yet meet ChatGPT publishing checks and meets Claude publishing checks. Passing these checks does not guarantee marketplace approval.

How clear is Lyon's MCP tool documentation?

As of October 14, 2026, Lyon scores 67/100 in Manufact's review of tool titles, descriptions, input and output schemas, and behavior annotations. The review covers 13 of 13 discovered tools. The quality score measures documentation clarity; runtime behavior and marketplace readiness require separate checks.

How can Lyon improve its MCP documentation?

show_lyon_weather is the lowest-scoring reviewed tool at 44/100. 0 of 7 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values. Open its review for feedback and a copyable fix prompt, then rerun the documentation review after updating your tool metadata.

Not your MCP?

Review any public or OAuth MCP server for protocol compatibility, tool documentation, and ChatGPT and Claude publishing readiness. No account required.

Get your MCP score

Back to leaderboard

Opening your score report…

Title94/100

Display Map

The title clearly communicates the tool’s action and subject. Keep it concise.

Description91/100

The description explains the capability, when to use it, and what to expect.

Inputs75/100

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

title

Optional heading shown above the map

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

items › items › title

Item title

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

items › items › description

Short supporting text

Explain the meaning of this value, not just its name.

items › items › imageUrl

Image URL (https). Supplied by you — no lookup is performed.

Clear enough to supply this argument.

items › items › badge

Small label, e.g. a price or a tag

Clear enough to supply this argument.

items › items › action › label

Button label

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

items › items › action › prompt

Follow-up message sent to the assistant when clicked

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

items › items › lat

Latitude

Clarify units, where to obtain this value, or conventions not already expressed in the schema.

items › items › lng

Longitude

Clarify units, where to obtain this value, or conventions not already expressed in the schema.

items › items › location

Full address or location description

Clear enough to supply this argument.

items › items › rating

Rating if available

Clarify units, where to obtain this value, or conventions not already expressed in the schema.

items › items › tags

Tags or categories

Clear enough to supply this argument.

Annotations75/100

Declare idempotentHint based on the tool’s actual behavior.

{
  "title": "Display Map",
  "readOnlyHint": true,
  "openWorldHint": false,
  "destructiveHint": false
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "display_lyon_map",
  "description": "Display places on an interactive map of Lyon. Each item needs a `title` and its `lat`/`lng` coordinates — this tool renders only what you give it and never looks anything up. Use the search_lyon_places tool first if you don't have coordinates.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "items"
    ],
    "properties": {
      "items": {
        "type": "array",
        "items": {
          "type": "object",
          "required": [
            "lat",
            "lng"
          ],
          "properties": {
            "lat": {
              "type": "number",
              "description": "Latitude"
            },
            "lng": {
              "type": "number",
              "description": "Longitude"
            },
            "tags": {
              "type": "array",
              "items": {
                "type": "string"
              },
              "description": "Tags or categories"
            },
            "badge": {
              "type": "string",
              "description": "Small label, e.g. a price or a tag"
            },
            "title": {
              "type": "string",
              "description": "Item title"
            },
            "action": {
              "type": "object",
              "required": [
                "label",
                "prompt"
              ],
              "properties": {
                "label": {
                  "type": "string",
                  "description": "Button label"
                },
                "prompt": {
                  "type": "string",
                  "description": "Follow-up message sent to the assistant when clicked"
                }
              },
              "description": "Optional call-to-action"
            },
            "rating": {
              "type": "number",
              "description": "Rating if available"
            },
            "imageUrl": {
              "type": "string",
              "description": "Image URL (https). Supplied by you — no lookup is performed."
            },
            "location": {
              "type": "string",
              "description": "Full address or location description"
            },
            "description": {
              "type": "string",
              "description": "Short supporting text"
            }
          }
        },
        "description": "Places to display on the map. `title`, `lat` and `lng` are required on each item."
      },
      "title": {
        "type": "string",
        "description": "Optional heading shown above the map"
      }
    }
  },
  "annotations": {
    "title": "Display Map",
    "readOnlyHint": true,
    "openWorldHint": false,
    "destructiveHint": false
  }
}