Skip to main content
Glama
Sign In
mcp-server-demo

mcp-server-demo

by charley-forey
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_workflow_status

Check the current workflow step and the required sequence of tools to stay on track in the multi-step process from OpenAPI validation to GitHub upload.

Instructions

Return the current workflow step and the required order of tools.

Use this to keep the user/agent on track. Order: 1. validate_openapi → 2. prompt_mcp_developer_context → 3. propose_endpoint_bundles → 4. select_endpoint_bundle → 5. generate_mcp_server → 6. upload_to_github.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_workflow_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior3/5

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

No annotations are provided, so the description must disclose behavior. It indicates the tool returns status information but does not explicitly state whether it is read-only or has side effects. For a status query, this is acceptable but could be more explicit.

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?

The description is concise: two sentences plus the ordered list. It front-loads the purpose and provides essential details without unnecessary words.

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

Completeness5/5

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

Given the tool's simplicity (no parameters, no output schema), the description fully covers what an agent needs: what it returns and why to use it. It is complete for the tool's complexity.

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 tool has no parameters, so schema coverage is effectively 100%. The description adds meaning by explaining what the tool returns (current step and order), which is not evident from the empty schema.

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 explicitly states the tool returns the current workflow step and the required order of tools. It clearly identifies the resource (workflow status) and action (return), distinguishing it from sibling tools like reset_workflow or generate_mcp_server.

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 advises to 'use this to keep the user/agent on track' and provides the exact sequence of tools. While it does not explicitly state when not to use it, the context implies it is for progress checking, making usage clear.

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