Skip to main content
Glama
Sign In
ccg-mcp-tool

ccg-mcp-tool

by diaz3618
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

agent-status

Check the status of multi-agent orchestration sessions. Supply a session ID for details or leave blank to list recent sessions.

Instructions

Check status of multi-agent orchestration sessions. Provide a sessionId to get details, or omit to list recent sessions. Current agent mode: read-only.

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": "agent-status"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionIdNoSession ID to query (e.g., 'ses_abc123'). Omit to list recent sessions.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.1

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description mentions read-only mode but lacks details on authentication, rate limits, error handling, or what happens with invalid sessionIds.

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 two sentences, front-loaded, and every word serves a purpose. No fluff.

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 status check tool with one optional parameter, the description covers the key functionality and usage. It could mention return format or pagination but is largely complete.

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 coverage is 100% and the description adds value by explaining the effect of providing vs omitting the sessionId, but does not add meaning beyond what the schema already provides.

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 clearly states the tool checks status of multi-agent orchestration sessions, with two distinct usage modes (with or without sessionId). It uses specific verb+resource and distinguishes itself from sibling tools.

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 provides clear context on when to use the tool (checking session status) and the two modes, but does not explicitly state when not to use or mention alternatives among siblings.

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