Get the pip install command and mcpServers JSON needed to connect platworks to any MCP-capable editor or client.
Get install commands and the MCP client config for wiring platworks in.
Copy-pasteable: a pip install line and the mcpServers JSON for any MCP-capable editor or client.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It makes the behavior plain: the tool returns copy-pasteable commands and JSON, implying a non-destructive read operation. It does not claim to execute an installation or modify anything, so the behavior is transparent enough for a 0-parameter informational tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences with no filler. The first sentence states the tool's core purpose, and the second adds concrete details about the return content. The structure is fully front-loaded and every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter tool with no output schema, the description provides everything an agent needs: purpose, output format, and applicability. There is no missing information that would prevent correct invocation or interpretation of the result.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parametersainer and schema coverage is effectively complete. The baseline of 4 applies because there is nothing for the description to clarify about parameters; the tool simply needs no input.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool returns install commands and MCP client configuration for connecting platworks. The verb 'Get' identifies an informational retrieval action锁定 to a specific resource, and the content (pip install line, mcpServers JSON) distinguishes it from the unrelated sibling tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description communicates when to use this tool: when the user needs installation commands or client configuration for MCP support. It does not explicitly exclude alternatives, but none of the sibling tools serve a similar purpose, so the context is clear enough without additional routing guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.