reloadium.com WebMCP Tools, Schemas & Agent Capabilities

reloadium.com

live Unverified (seed import) AI & Agents 204 tools imperative implementation

Paste a topic, URL, or PDF/TXT/MD — get a multi-episode AI podcast with audio, transcripts, timelines and quizzes. 60+ languages.

First seen 2026-11-05 · Last seen 2026-11-05 · Source: webmcp.com

Answer 67 · Act 127 · Transact 10 · Score: Not yet scored

Tool inspector

showMap

act imperative

Show an interactive map card in the chat with one or more pins, optionally connected by a route. Renders as a small card the user can click to expand full-screen — use this instead of just describing locations in text whenever the answer is about specific real-world places. Provide pins as {name, lat, lng} — omit lat/lng to have the name geocoded automatically (free OpenStreetMap lookup). IMPORTANT: bare landmark names are sometimes ambiguous against unrelated same-named places elsewhere in the world (e.g. 'The Louvre' alone can match an obscure peak on another continent) — always include enough context to disambiguate when you know it, e.g. 'Louvre Museum, Paris' rather than 'The Louvre'. But do NOT go further and add a street address on top of a venue name — 'venue, city' is the sweet spot; 'venue, street address, city' geocodes WORSE (the geocoder can't match name+address in one query; the tool falls back to simplified retries but each costs an extra round-trip). Use a street address alone (no venue name) when the address IS the place being pinned. The tool also biases each pin's search toward previously resolved pins in the same call, so listing an unambiguous pin (e.g. 'Eiffel Tower') before ambiguous ones in the same city helps. Give each pin a 'category' for its marker color: default, food, lodging, activity, transport, event, landmark, nature. If you already have the user's own coordinates (e.g. from a prior getUserLocation call) and it's relevant to show where they are relative to the other pins (nearby places, distance context), add one more pin for it with isUserLocation:true and their lat/lng — it renders as a distinct 'you are here' marker instead of a category color; don't call getUserLocation again just to add this if you already have the coordinates in the conversation. For a 'near me' / category request (e.g. 'gas stations near me'), NEVER pass bare category words as pin names (e.g. {name:'Gas station'}) — with no real place name to search for, the…

Page: /

Input schema

Property	Type	Required	Description
`title`	string	no	—
`pins`	array	yes	—
`route`	object	no	—

Raw JSON schema

{
  "type": "object",
  "properties": {
    "title": {
      "type": "string"
    },
    "pins": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "name": {
            "type": "string"
          },
          "lat": {
            "type": "number"
          },
          "lng": {
            "type": "number"
          },
          "address": {
            "type": "string",
            "description": "Optional street address (e.g. 'Grodzka 43, Kraków') used as a geocoding fallback when the bare name doesn't resolve — keep it OUT of `name`, which stays the display label. Ignored when lat/lng are given."
          },
          "description": {
            "type": "string"
          },
          "category": {
            "type": "string",
            "enum": [
              "default",
              "food",
              "lodging",
              "activity",
              "transport",
              "event",
              "landmark",
              "nature"
            ]
          },
          "isUserLocation": {
            "type": "boolean",
            "description": "True only for a pin representing the user's own current position (e.g. from getUserLocation) — renders with a distinct 'you are here' marker instead of a category color."
          }
        },
        "required": [
          "name"
        ]
      }
    },
    "route": {
      "type": "object",
      "properties": {
        "ordered": {
          "type": "boolean"
        },
        "mode": {
          "type": "string",
          "enum": [
            "driving",
            "walking",
            "cycling",
            "flight"
          ]
        },
        "legs": {
          "type": "array",
          "items": {
            "type": "object",
            "properties": {
              "from": {
                "type": "number"
              },
              "to": {
                "type": "number"
              },
              "mode": {
                "type": "string",
                "enum": [
                  "driving",
                  "walking",
                  "cycling",
                  "flight"
                ]
              }
            },
            "required": [
              "from",
              "to"
            ]
          }
        }
      }
    }
  },
  "required": [
    "pins"
  ]
}