platform.launch.readiness
GET /v1/platform/launch/readiness
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| body | No | ||
| query | No | ||
| pathParams | No |
ClawSpan ShardLink MCP
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
D1/5.0
Behavior1/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description should disclose side effects or read-only nature. The description only gives the HTTP method 'GET', but does not clarify that it is a read-only operation, nor does it describe any behavior or constraints.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness1/5
Is the description appropriately sized, front-loaded, and free of redundancy?
While extremely short, the description under-specifies the tool to the point of uselessness. It does not earn its place as it provides no actionable information beyond the name.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness1/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity (no output schema, no annotations, three parameters with no description), the description is wholly inadequate. It lacks any complete information needed for an agent to correctly select and invoke the tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters1/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema defines three parameters (body, query, pathParams) as empty objects with no described properties, and the description offers zero explanation. With 0% schema description coverage, the description fails entirely to add meaning.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose1/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description is merely the HTTP method and path ('GET /v1/platform/launch/readiness'), which is a tautology of the tool name and provides no indication of what the tool actually does or what resource it acts upon.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines1/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No usage context is provided. There is no guidance on when to use this tool, prerequisites, or how it differs from sibling tools like `workspaces.launch.capability_status` or `workspaces.launch.curation`.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
C2.1/5.0
Disambiguation5/5
All 43 tools are clearly disambiguated by a hierarchical dot-separated naming scheme (e.g., workspaces.billing.accounts.create). Each tool targets a unique combination of resource and action, with no apparent overlap or ambiguity.
Naming Consistency5/5
The naming follows a consistent <domain>.<subdomain>.<action> pattern, with actions as verbs (create, list, revoke, etc.). The use of underscores within the final component is uniform, making the pattern predictable across all tools.
Tool Count4/5
At 43 tools, the server covers a broad scope (contracts, billing, workspaces, tasks, etc.), which justifies the high count. However, it is slightly above the typical well-scoped range of 3-15, risking overwhelm.
Completeness3/5
The tool set covers many operations for billing, tasks, and workspace management, but lacks fundamental create/update/delete for some core resources (e.g., no workspace.create or instruments.delete). Agents may encounter dead ends.