Delivery-capacity landing governor

proxy_checkout

Scoped sparse checkout through the stock-git proxy ($0.01/proxied checkout x402; requires an active Meter + Verdicts subscription). Scope paths rejecting '.', '..', absolute and '.git/' are refused.

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": {
      "project_id": "<project_id>",
      "operator": "<operator>",
      "scope": "<scope>"
    },
    "name": "proxy_checkout"
  }
}

Input Schema

Name	Required	Description	Default
`scope`	Yes
`operator`	Yes
`project_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

B3.3/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and discloses real behavioral facts: a per-checkout charge, a required subscription, and a validation rule set that refuses '.', '..', absolute paths and '.git/' entries. It does not say what the call returns or what it does to the working tree, which keeps it short of 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact sentences with the core action front-loaded and no filler. The density of parenthetical pricing/billing detail makes it slightly harder to parse but nothing is redundant.

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

Completeness2/5

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

A 3-required-parameter mutation-adjacent tool with no annotations, no output schema, and 0% schema coverage needs more than this. Missing are the meaning of project_id/operator, what a successful checkout produces, and any auth or error semantics beyond path rejection.

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 description coverage is 0% across 3 required parameters, so the description must compensate. It only touches 'scope' indirectly via the path-rejection rules; 'project_id' and 'operator' are completely undefined in both schema and description, leaving an agent to guess their meaning and format.

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?

States a specific verb and resource: a scoped sparse checkout performed through the stock-git proxy. It names the mechanism and scope restriction clearly enough to distinguish it from the governor_/verdict_ siblings, though the term 'stock-git proxy' is unexplained jargon.

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

Usage Guidelines3/5

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

Gives prerequisites (active Meter + Verdicts subscription) and a price ($0.01/proxied checkout via x402), which implies when the call is appropriate. However, it never states when to use this versus a plain checkout or any alternative, and no sibling overlaps are addressed.

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

All Delivery-capacity landing governor 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?