Skip to main content
Glama
ElonJask

ProxyPin MCP Server

by ElonJask

search_requests

Search captured HTTP traffic by keyword to analyze API structures and generate client-side code from network history.

Instructions

Search requests by keyword.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keywordYes
search_inNoall
limitNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Implementation of the `search_requests` tool, which searches for requests based on a keyword and optional search area/limit.
    @mcp.tool()
    def search_requests(
        keyword: str,
        search_in: str = "all",
        limit: int = 20,
    ) -> str:
        """Search requests by keyword."""
        if not keyword.strip():
            return _json_response({"error": "keyword is required"})
    
        normalized_search_in = search_in if search_in in VALID_SEARCH_AREAS else "all"
        normalized_limit = _bounded_limit(limit, default=20, maximum=100)
        results = reader.search(keyword, normalized_search_in, normalized_limit)
        return _json_response(results)
Behavior1/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only states the action ('search') without any information about permissions needed, rate limits, pagination behavior, what happens on no matches, or response format. For a search tool with no annotation coverage, this is inadequate.

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 extremely concise at three words, with zero wasted language. It's front-loaded with the core action and resource. While under-specified, it's structurally efficient.

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

Completeness2/5

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

Given 3 parameters with 0% schema coverage, no annotations, and sibling tools that might overlap, the description is incomplete. It doesn't explain the search scope, result format, or how parameters interact. The presence of an output schema helps, but the description should provide more context for effective tool selection and use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the schema provides no parameter descriptions. The description mentions 'keyword' but doesn't explain what 'search_in' or 'limit' do, their allowed values, or how they affect results. It adds minimal value beyond the parameter names visible in the schema.

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

Purpose3/5

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

The description 'Search requests by keyword' clearly states the verb (search) and resource (requests), but it's vague about scope and doesn't distinguish from sibling tools like 'list_requests' or 'get_request'. It provides basic purpose but lacks specificity about what kind of requests or search context.

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?

No guidance is provided about when to use this tool versus alternatives like 'list_requests' or 'get_request'. The description doesn't mention prerequisites, context for keyword searching, or any exclusions. It leaves the agent to infer usage from the tool name alone.

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/ElonJask/proxypin-mcp'

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