Skip to main content
Glama
Sign In
chc-social

chc-social

by CHCDOLADEEPSEEKMKSEC
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

social_networks

Lists available social networks, their capabilities, and credential status to verify setup before posting or scheduling.

Instructions

List networks, capabilities and whether credentials are present.

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_networks"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; the verb "List" does establish this is a non-mutating read. It adds the useful disclosure that the result includes a credential-presence flag, which is genuinely behavioral information. It says nothing about pagination, ordering, or whether any authentication is required to enumerate the credentials status.

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?

One short sentence with no filler, and the core content is front-loaded. It is arguably too compressed rather than padded, with the credential-presence clause tacked on without explaining its significance.

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

Completeness3/5

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

For a zero-parameter, no-annotation, no-output-schema read tool, the definition is minimal but not unreasonable. Since there is no output schema, the description should at least sketch the shape of the returned list — one record per network, what "capabilities" look like — and it does not.

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 takes zero parameters, so there is no parameter semantics to compensate for; the schema is an empty object and baseline is 4. The description correctly implies no input is needed, though it does not explicitly say the call is unfiltered and returns everything.

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

Purpose3/5

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

"List networks, capabilities and whether credentials are present" gives a verb plus three items of content, so the agent knows it is a read of network inventory. However, "networks" and "capabilities" are left unqualified, and nothing in the sentence distinguishes this from siblings such as social_account or social_read, which likely touch the same domain.

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?

There is no when-to-use guidance, no precondition, and no named alternative among the many social_* siblings. The agent must infer that this is the discovery step before calling social_account or social_post, which is not stated anywhere.

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