Skip to main content
Glama

AgentReady Woo

by xyz.utilityhouse
OverviewDiscussionsAdmin

start_woo_release_verification

Start an ownership-authorized Release Gate run. Requires a bearer token with release:start.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeYesRequired safety mode. The only accepted value is owned-safe-active, which requires verified store ownership before the run starts.
store_idYesAgentReady store identifier owned by the authenticated account. Use the stored identifier, never a store URL, secret, or customer value.
baseline_run_idNoOptional prior Release Gate run identifier from the same owned store to use as the comparison baseline; omit when no valid baseline exists.
idempotency_keyYesCaller-generated retry key for this exact start request. Reuse it only when retrying the same operation; do not place credentials or customer data in it.
requested_familiesYesOne or more protocol families the owner authorizes this Release Gate run to verify: woo, robots, jsonld, mcp, ucp, or acp.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / baseline_run_id / description
      Added value: +"Optional prior Release Gate run identifier from the same owned store to use as the comparison baseline; omit when no valid baseline exists."
    • addedInput schema / properties / idempotency_key / description
      Added value: +"Caller-generated retry key for this exact start request. Reuse it only when retrying the same operation; do not place credentials or customer data in it."
    • addedInput schema / properties / mode / description
      Added value: +"Required safety mode. The only accepted value is owned-safe-active, which requires verified store ownership before the run starts."
    • addedInput schema / properties / mode / type
      Added value: +"string"
    • addedInput schema / properties / requested_families / description
      Added value: +"One or more protocol families the owner authorizes this Release Gate run to verify: woo, robots, jsonld, mcp, ucp, or acp."
    • addedInput schema / properties / store_id / description
      Added value: +"AgentReady store identifier owned by the authenticated account. Use the stored identifier, never a store URL, secret, or customer value."
  2. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already indicate this is a write operation (readOnlyHint=false) and non-destructive. The description adds the auth requirement (bearer token with release:start), which is useful, but does not elaborate on side effects or the meaning of openWorldHint. It is consistent with annotations, so no contradiction.

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 sentence that is front-loaded with the core purpose and contains no filler. It is appropriately concise.

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?

Given the output schema exists and annotations cover safety, the description is minimal but adequate for initiating a run. However, it does not explain the openWorldHint or mention that this likely starts an asynchronous process, leaving some context implicit. Overall, it is sufficient but not rich.

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%, so the baseline is 3. The description adds no parameter-specific information; all semantics are already in the schema. The description does not compensate for anything because nothing is missing.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool starts an ownership-authorized Release Gate run, using a specific verb and resource. It does not mention sibling tools or differentiate itself, but the purpose is unambiguous.

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 its siblings (claim, get, preflight, scan). It only says 'start a run,' implying the obvious, but does not state prerequisites beyond a bearer token or indicate when alternatives are more appropriate.

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

All AgentReady Woo 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