Skip to main content
Glama
Sign In
timps-swarm

timps-swarm

by Sandeeprdy1729
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

timps_web_scraping

Generate web scrapers using Playwright, Scrapy, or httpx with anti-bot configuration and data extraction logic to pull structured content from websites.

Instructions

Generate Playwright/Scrapy/httpx scrapers with anti-bot config and data extraction logic.

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": "timps_web_scraping"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestNoPlain-English task or context for the agent.
languageNoPrimary programming language (default: python).python

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.2.1

TDQS

B3.2/5.0
Behavior2/5

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

Since no annotations are present, the description carries the full burden of behavioral disclosure. It does not mention whether the tool outputs code, writes files, requires network access or API keys, or any side effects. It only hints at the content of generated scrapers but not the tool's own behavior.

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 a single, front-loaded sentence that starts with the verb 'Generate' and contains no unnecessary words. It is maximally concise and well-structured.

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 the tool's complexity (code generation) and lack of output schema and annotations, the description is incomplete. It doesn't explain the expected output format, how the request should be structured, or any error handling/limitations. An agent would struggle to use it correctly.

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

Parameters3/5

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

Schema coverage is 100% with descriptions for both request and language. The description adds no additional parameter semantics beyond what the schema already provides, so the baseline of 3 is appropriate.

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 clearly states the tool generates scrapers using specific libraries (Playwright/Scrapy/httpx) with anti-bot config and data extraction logic. This is a specific verb+resource combination that distinguishes it from sibling tools like timps_browser_automation or timps_web_search.

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 on when to use this tool versus alternatives, no mention of prerequisites, exclusions, or context. It's a bare declarative statement with no usage direction.

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