Skip to main content
Glama
Sign In
cws-mcp

cws-mcp

by mikusnuz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get

Fetch publication status through v2 (alias of status). Version 2 no longer returns listing metadata or supports projection; use get-metadata-ui for draft listing text.

Instructions

Fetch publication status through v2 (alias of status). Version 2 no longer returns listing metadata or supports projection; use get-metadata-ui for draft listing text.

Input Schema

NameRequiredDescriptionDefault
itemIdNoExtension item ID
projectionNoRemoved in 2.0; use get-metadata-ui for current draft listing text
publisherIdNoPublisher ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.0.2
    • changedInput schema / properties / itemId / description
      Previous value: -"Extension item ID (defaults to CWS_ITEM_ID env var)"New value: +"Extension item ID"
    • changedInput schema / properties / projection / description
      Previous value: -"Metadata projection to fetch (defaults to DRAFT)"New value: +"Removed in 2.0; use get-metadata-ui for current draft listing text"
    • addedInput schema / properties / publisherId
      Added value: +{
+  "description": "Publisher ID",
+  "type": "string"
+}
  2. First observedv1.4.1

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description does carry real weight: it discloses a v2 behavioral regression (no listing metadata) and that `projection` is unsupported. It says nothing about auth requirements, what the response actually contains, or whether missing IDs are required, which are material gaps for an otherwise read-shaped call.

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 short sentences with the identity/alias claim front-loaded and the alternative named second. No filler, though the version-2 constraint is repeated once across both sentences.

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?

Covers the deprecation story and the sibling alternative, which is the main complexity here. But with no annotations, no output schema, and zero required parameters, an agent still lacks guidance on whether `itemId` must be supplied and what the returned status looks like.

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 description coverage is 100%, so the schema already documents all three parameters, including the deprecation note on `projection`. The description only reinforces the `projection` removal and adds no detail on `itemId` or `publisherId` semantics, so it does not exceed the baseline.

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 ("Fetch publication status through v2") and immediately clarifies that it is an alias of the sibling `status`, which disambiguates a very generic tool name. It also distinguishes itself from `get-metadata-ui` by saying listing metadata is no longer returned here.

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?

Explicitly routes the agent away from this tool for draft listing text ("use get-metadata-ui") and tells it that `status` is an equivalent alias. It stops short of stating when/why an agent would prefer this over `status`, but the alias note makes that moot.

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

Deploy Server

Other Tools