Skip to main content
Glama
Sign In
tripadvisor-mcp

tripadvisor-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Verify the ContextMint Bridge connection end-to-end

ta_web_healthcheck
Read-onlyIdempotent

Diagnose TripAdvisor-MCP bridge failures by round-tripping a test URL through your browser tab. Returns bridge role, port, version, extension status, and hints identifying which hop broke.

Instructions

Round-trips a small public www.tripadvisor.com URL (/) through ContextMint Bridge (your signed-in browser tab) and returns diagnostics: the bridge's role (host/peer/null), port, version, the extension link (linked / pair pending / not attached / never answered), the elapsed round-trip time, and a plain-English hint distinguishing 'bridge never came up' from 'extension not connected' from 'this browser can't serve a capability' from 'real www.tripadvisor.com-side problem'. Read-only, no auth required. Call this when a real tool fails and you want to know which hop broke.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ta_web_healthcheck"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Addedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations' readOnly/openWorld/idempotent hints, the description adds that no auth is required and, critically, discloses the full diagnostic payload and the enumerated failure states the hint distinguishes ('bridge never came up' vs 'extension not connected' vs 'browser can't serve a capability' vs 'real tripadvisor-side problem'). With no output schema, this behavioral disclosure is valuable and non-redundant.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The action and return payload are front-loaded, and the final sentence provides the call condition. The first sentence is long and clause-heavy, but nearly every clause carries substantive information (payload contents, failure-state taxonomy), so little is wasted.

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?

For a no-input, no-output-schema diagnostic tool, the description covers what it does, what it returns, the states it discriminates, and when to invoke it. Nothing an agent needs to call it 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?

The tool takes zero parameters, so there is nothing for the description to add and the baseline of 4 applies. The description correctly signals there is no input to supply.

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?

The description states a precise verb and resource ('Round-trips a small public www.tripadvisor.com URL through ContextMint Bridge') and enumerates exactly what the tool returns (role, port, version, extension link state, round-trip time, hint). This is unmistakably a diagnostic/healthcheck tool, cleanly separable from the location-data siblings.

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?

It gives an explicit trigger: 'Call this when a real tool fails and you want to know which hop broke.' That routes the agent directly to this tool as the fallback when a sibling fails, which is exactly the when-to-use guidance needed.

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

Deploy Server

Other Tools