Skip to main content
Glama
Sign In
@launchlint/mcp

@launchlint/mcp

by TheWinters12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

get_project_status

Read-onlyIdempotent

Retrieve the current status of a project by providing its project key, using LaunchLint's cloud-based analysis.

Instructions

Use the authenticated LaunchLint cloud tool get_project_status.

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": {
      "projectKey": "<projectKey>"
    },
    "name": "get_project_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectKeyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.5

TDQS

D1/5.0
Behavior1/5

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

The description adds no behavioral information beyond what annotations already provide (readOnlyHint, idempotentHint, etc.). It does not disclose any additional traits.

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?

One sentence that is under-specified, wasting the opportunity to convey useful information. It is not helpfully concise.

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?

The description fails to explain what the tool returns, how to interpret status, or any contextual details. With no output schema and minimal description, the agent cannot use it effectively.

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?

Schema description coverage is 0% and the description does not explain the projectKey parameter or its purpose. No added meaning beyond schema constraints.

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 merely restates the tool name and says 'use this tool'. It does not specify the action (getting status of a project) or what resource is involved, making it tautological.

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 guidance on when to use this tool versus siblings like list_projects or start_workspace_scan. No context or prerequisites provided.

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