Regresco

Create project

create_project

Create a Regresco project for a web app's staging or preview URL. The URL must be public http(s) and is checked for reachability; private network and cloud metadata addresses are refused. Uses one project from the account's plan limit.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "stagingUrl": "<stagingUrl>"
    },
    "name": "create_project"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes	Project name, usually the app's name
`stagingUrl`	Yes	Public base URL of the staging or preview environment, e.g. https://staging.example.com

Output Schema

Name	Required	Description	Default
`project`	Yes
`projectsUsed`	Yes
`projectsLimit`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare write, non-idempotent, open-world, non-destructive, so the safety profile is covered. The description adds genuinely useful behavior beyond that: outbound reachability validation, SSRF-style rejection of private/metadata addresses, and consumption of a quota slot. It doesn't cover failure responses or permissions, keeping it from a 5.

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?

Three sentences, front-loaded with the action and resource, then constraints, then the quota side effect. Every sentence carries distinct information with no redundancy.

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?

Output schema exists, so return values needn't be explained, and the two required parameters are fully documented. The mutating, quota-consuming nature is disclosed; only error behavior and any auth expectations are left implicit.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real constraints the schema omits: stagingUrl must be a public, reachable http(s) endpoint and is validated at call time. That clarifies the 'format: uri' field with semantics the schema does not express.

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?

Specific verb (Create) plus resource (a Regresco project) plus the scope qualifier "for a web app's staging or preview URL". An agent can distinguish this from get_project, list_projects, and update_project without opening any schema.

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

Usage Guidelines4/5

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

Gives clear preconditions for correct use: the URL must be public http(s) and is reachability-checked, private network and cloud metadata addresses are refused, and the call consumes one project from the plan limit. It stops short of naming sibling alternatives or when-not-to-use cases, but the creation context is unambiguous.

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

All Regresco tools Inspect

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

Need Help?