← WebMCP Directory

Tool tree

signpost.ziola.dev

Developer ToolsTools verified
Website
Signpost points WebMCP agents to the sites that can do what they need. The agent decides what comes next.
Explore capabilities
    resolve_surfaceAction

    Find which provider surface can perform ONE capability you need, described in your own words. Input: { capability: "<a single capability need, e.g. order a coffee or book a haircut>" }. Returns candidates with { surface_url, capability } and an optional transport. Missing transport or "webmcp" means navigate to the surface and discover its native tools. Transport "mcp-streamable-http" means surface_url is an MCP endpoint: use an MCP client in your host to connect and discover its tools; browser navigation alone does not connect it. If your host cannot connect, report that limitation. This resolver is STATELESS and JOURNEY-BLIND: it does not know your overall objective, does not track progress, order, or history, and cannot tell you what to do next. Call it once per capability need. You own the plan and the sequencing; Signpost only points to where a single capability can be performed.

    View tool JSON
    {
      "name": "resolve_surface",
      "kind": "act",
      "impl": "imperative",
      "description": "Find which provider surface can perform ONE capability you need, described in your own words. Input: { capability: \"<a single capability need, e.g. order a coffee or book a haircut>\" }. Returns candidates with { surface_url, capability } and an optional transport. Missing transport or \"webmcp\" means navigate to the surface and discover its native tools. Transport \"mcp-streamable-http\" means surface_url is an MCP endpoint: use an MCP client in your host to connect and discover its tools; browser navigation alone does not connect it. If your host cannot connect, report that limitation. This resolver is STATELESS and JOURNEY-BLIND: it does not know your overall objective, does not track progress, order, or history, and cannot tell you what to do next. Call it once per capability need. You own the plan and the sequencing; Signpost only points to where a single capability can be performed.",
      "inputSchema": {
        "type": "object",
        "properties": {
          "capability": {
            "type": "string",
            "description": "A single capability need, in natural language. Not the whole objective — one thing you want to do."
          }
        },
        "required": [
          "capability"
        ],
        "additionalProperties": false
      },
      "page": "/"
    }