Skip to main content
Glama
Sign In
chc-social

chc-social

by CHCDOLADEEPSEEKMKSEC
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

social_queue

Lists queued social media jobs and drains the ones that are due, helping you review pending posts and process scheduled actions.

Instructions

List queued jobs, or drain the ones that are due.

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": "social_queue"
  }
}

Input Schema

NameRequiredDescriptionDefault
drainNo
stateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full behavioral burden. It does not explain what 'drain' actually does, whether it deletes or executes jobs, whether it is destructive, what 'due' means, or what permissions and side effects are involved.

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

Conciseness4/5

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

The description is a single compact sentence with no filler and the main operations are front-loaded. Its brevity is efficient, though it comes at the cost of clarity around 'drain'.

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

Completeness2/5

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

For a tool with two wholly undocumented parameters, no annotations, and no output schema, this description is too thin. It omits critical behavior around draining, job state filtering, side effects, and return values.

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

Parameters2/5

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

Schema description coverage is 0%, yet the description only indirectly implies that 'drain' toggles a drain mode and never explains the 'state' parameter. With both parameters undocumented in the schema, the description should compensate but leaves their meaning largely unspecified.

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

Purpose4/5

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

The description names two concrete operations on a specific resource: listing queued jobs and draining due jobs. It is understandable without opening the schema, though 'drain' remains jargon and the description does not distinguish this tool from queue-related siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It implies that listing is the default and draining applies to due jobs, but gives no explicit guidance on when to choose each mode. It also provides no alternatives or conditions for using this tool versus related social_* tools.

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