Skip to main content
Glama
Sign In
AI OS MCP Server

AI OS MCP Server

by cockimitu-ops
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_project_status

Retrieve the current status of a specified project by name to know if it's active, paused, or ended.

Instructions

Fetch the current status of one specific project by name, e.g. 'QuickTurnaroundGigs' or 'GetClean'.

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_name": "<project_name>"
    },
    "name": "get_project_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_nameYesThe project's name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description carries the burden, and it adequately conveys that this is a read-only fetch, not a mutation. However, it does not disclose behavior for unknown project names, exact matching, or the shape of the returned status value.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

One concise sentence packs in the verb, resource, scope, and examples without any waste. Every part of the sentence adds meaning.

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

Completeness4/5

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

For a simple one-parameter read-only tool, this description is largely sufficient. The main gap is that no output schema is present and the description does not describe what the returned status payload looks like, but the tool name and verb make the expected outcome reasonably clear.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already provides 100% description coverage for project_name. The description adds extra semantics by emphasizing that the parameter is the project name itself and giving realistic examples, which helps an agent format the value correctly.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Fetch'), names the exact resource ('current status of one specific project by name'), and gives concrete examples ('QuickTurnaroundGigs', 'GetClean'). This clearly differentiates it from siblings like list_projects, which would list multiple projects.

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?

The description clearly implies when to use it: when you need the status for a single known project. It does not explicitly name alternatives or say when not to use it, but the scope is clear enough for an agent to select it over a list/search tool.

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