Skip to main content
Glama

get_scraper_status

Check the health and configuration of the Bing Flights scraper to verify operational status and supported features.

Instructions

Check scraper health and configuration.

Returns: Dictionary with scraper status information including: - status: Current status ("healthy") - version: Scraper version - capabilities: Supported features

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'get_scraper_status' MCP tool, decorated with @mcp.tool() for registration. It returns a hardcoded dictionary with scraper status, version, and capabilities.
    @mcp.tool()
    def get_scraper_status() -> dict:
        """Check scraper health and configuration.
    
        Returns:
            Dictionary with scraper status information including:
            - status: Current status ("healthy")
            - version: Scraper version
            - capabilities: Supported features
        """
        return {
            "status": "healthy",
            "version": "1.0.0",
            "capabilities": {
                "one_way_search": True,
                "round_trip_search": True,
                "cabin_classes": [
                    "economy", "premium_economy", "business", "first"
                ],
                "max_results": 50,
                "headless_mode": True
            }
        }
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes the return format (a dictionary with specific fields) and implies a read-only operation, but lacks details on error handling, rate limits, authentication needs, or side effects. This is adequate but has clear gaps for a tool with no annotation coverage.

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?

The description is front-loaded with the core purpose in the first sentence, followed by a structured breakdown of the return values. Every sentence adds value without redundancy, making it efficient and well-organized for quick comprehension.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (0 parameters, output schema exists), the description is reasonably complete. It explains the purpose and output format, though it could benefit from more behavioral context (e.g., error cases). The output schema likely covers return details, reducing the need for extensive description.

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 input schema has 0 parameters with 100% coverage, so the schema fully documents the absence of inputs. The description doesn't need to add parameter information, and it appropriately focuses on the output. A baseline of 4 is justified since there are no parameters to explain.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose with a specific verb ('Check') and resource ('scraper health and configuration'), making it immediately understandable. However, it doesn't differentiate from the sibling tool 'search_flights' (which appears unrelated), so it doesn't fully earn a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives or in what context. It simply states what the tool does without any usage instructions, prerequisites, or exclusions, leaving the agent to infer appropriate usage scenarios.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/chonseng/bing-flights-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server