Skip to main content
Glama
Sign In
webscope

webscope

by partprogramming09
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
WEBSCOPE_MANIFESTNoPath to the Webscope manifest file (webscope.json). Instead of passing --manifest you can set the environment variable WEBSCOPE_MANIFEST.
WEBSCOPE_ESCRITURANoSet to 1 to enable the correr_escritura tool, which allows running write scripts declared in the manifest. Only needed if a script declares 'escribe' and you want to allow it.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}
prompts
{}
resources
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
searchA

Where a text is defined or used: lines grouped by file, most cited first (concise: 5 files). Case-insensitive. Use it instead of grep. To see the code use read. Read-only, inside the root; skips secrets (.env, *.key...).

readA

Only a chunk of a file: the function or class symbol (PHP, TS, JS, Vue, Python; list = several in one call), the section of a .md, a range lines, or from a log the last tail or those containing contains; without anything, the file index. Use it instead of Read, cat or sed. Read-only, inside the root; does not read secrets.

runA

Runs a read-only script from the manifest: exit code and trimmed output. Without name it lists them. Use it instead of Bash for what a script covers. No shell; rejects absolute paths, .. and anything that writes (goes through run_write).

Prompts

Interactive templates invoked by user choice

NameDescription
sessionLoads webscope's memory (templates, flows, findings, test menu and rules) and sets the budget protocol before touching the browser.
walkthroughWalks a frontend module live (list, create ZZ_E2E, edit, verify, delete, clean up) with Chrome and the webscope scripts, and summarizes only what fails.

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

TDQS

A4.2/5.0

Scored across 3 tools

Disambiguation5/5

search, read, and run have clearly distinct roles—locating text, reading file content, and executing read-only scripts—and the descriptions explicitly steer agents away from overlap (e.g., 'To see the code use read', 'use it instead of grep'). No tool pair does the same job.

Naming Consistency5/5

All tools use a single lowercase verb (search, read, run), a consistent and predictable convention. There is no mixed casing or noun/verb style inconsistency.

Tool Count5/5

Three tools is well-scoped for a focused read-only code exploration server; each tool is distinct and earns its place. The count is not thin because each tool packs several related capabilities (read covers symbols, ranges, sections, logs, and index).

Completeness4/5

The surface covers text search, file/symbol/range reading, and read-only script execution for codebase exploration. A minor gap is the lack of a dedicated filename/glob search, though read's file index and search partially cover that need.

Maintenance

ActivityNo data
ResponsivenessSyncing

Resources