Skip to main content
Glama

MeshArc

by dev.mesharc
OverviewDiscussionsAdmin

Create a watched project

create_project

Create a project that watches a site over time: it is crawled on its schedule and each run is compared with the last, recording pages added, modified and removed. Use it when the request is to monitor or track a site; for a one-off read use crawl_site (keep_crawl_as_project can turn that into a project later), and check list_projects first so the site is not added twice. Creating it reads the site's robots.txt and sitemaps but fetches no pages; every run then spends credits per page. Refused when the plan's project limit is reached. Returns the project, whose id start_run takes to crawl it now.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoA name for the project; omit to use the site's host name.
seedYesWhere the crawl starts: a public site's URL or bare domain, e.g. 'https://example.com/blog/' or 'example.com'. The project covers that host.
configNoAny subset of the settings describe_project_config lists. For one section of a site pass include_paths, e.g. {"include_paths": ["/blog/*"]}; map_site shows the site's sections first. Omit for the defaults.
scheduleNoHow often it re-crawls on its own; 'manual' (default) runs only when start_run is called.manual

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / config / description
      Added value: +"Any subset of the settings describe_project_config lists. For one section of a site pass include_paths, e.g. {\"include_paths\": [\"/blog/*\"]}; map_site shows the site's sections first. Omit for the defaults."
    • addedInput schema / properties / name / description
      Added value: +"A name for the project; omit to use the site's host name."
    • addedInput schema / properties / schedule / description
      Added value: +"How often it re-crawls on its own; 'manual' (default) runs only when start_run is called."
    • addedInput schema / properties / schedule / enum
      Added value: +[
+  "manual",
+  "hourly",
+  "daily",
+  "weekly"
+]
    • addedInput schema / properties / seed / description
      Added value: +"Where the crawl starts: a public site's URL or bare domain, e.g. 'https://example.com/blog/' or 'example.com'. The project covers that host."
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations, it discloses important behavior: creation reads robots.txt and sitemaps but fetches no pages, each run spends credits per page, and creation is refused when the plan's project limit is reached. It also explains the return value enough to point the agent to start_run.

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 compact paragraph that front-loads the core purpose and then adds usage, side effects, limits, and return behavior with no filler. Every sentence carries actionable information for an agent.

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?

Despite having no output schema, the description explains what is returned (the project and its id for start_run). It also covers prerequisites, alternatives, operational cost, and plan limits, which is complete for a high-impact creation tool.

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 description coverage is 100%, so the input schema already documents all four parameters in detail. The description adds useful context about the project lifecycle but does not add syntax or per-parameter meaning beyond what the schema provides, so the baseline 3 applies.

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 specific verb and resource: creating a project that watches a site over time, crawling on a schedule and comparing runs. It also names the key siblings it is not (crawl_site, keep_crawl_as_project, list_projects), so an agent can distinguish it without opening schemas.

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 explicitly says when to use it (monitor or track a site) and when not to use it (one-off reads should use crawl_site, and keep_crawl_as_project can convert later). It also adds a concrete precondition: check list_projects first to avoid adding the same site twice.

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

All MeshArc toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources