Meta Council

Create Scope Baseline

create_scope_baseline

Save immutable scope, estimates and explicit plan versions/dates for an owned delivery group. Reuse request_id on retries; a new request_id captures a new baseline. Requires tickets:write.

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": {
      "root_id": "<root_id>",
      "request_id": "<request_id>",
      "label": "<label>"
    },
    "name": "create_scope_baseline"
  }
}

Input Schema

Name	Required	Description	Default
`label`	Yes
`root_id`	Yes
`request_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 21, 2026

TDQS

A4.2/5.0

Behavior5/5

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

The description carries the behavioral burden because annotations are all generic false hints. It discloses immutability, request_id-based retry/new-baseline semantics, and the required permission, which materially informs an agent about side effects and prerequisites.

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 with no filler: primary action, retry behavior, then auth requirement. The most important information is front-loaded.

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

Completeness3/5

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

The description covers action, safety, retry, and auth, but no output schema exists and root_id/label semantics are incomplete, so an agent still has to guess at two required inputs and the response shape. Adequate but with clear gaps.

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 coverage is 0% and only request_id is semantically explained via the retry/new-baseline guidance. root_id is only indirectly tied to 'an owned delivery group', and label is not explained at all, leaving two required parameters under-specified.

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 opens with 'Save immutable scope, estimates and explicit plan versions/dates', a specific verb and resource with clear object and ownership scope. It is immediately distinguishable from sibling get/list/compare_scope_baseline tools.

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?

It gives actionable guidance: use for an owned delivery group, reuse the same request_id on retries, and require tickets:write. It does not explicitly name alternative tools or state when not to use it, so it stops short of a 5.

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

All Meta Council 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?