Skip to main content
Glama
Sign In
chc-social

chc-social

by CHCDOLADEEPSEEKMKSEC
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

social_read

Read recent posts or messages from a specified social network, with an optional limit on how many items to return.

Instructions

Read recent posts/messages from a network.

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": {
      "network": "<network>"
    },
    "name": "social_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
networkYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, the description carries the full burden: 'Read' implies a non-mutating operation, which is the only behavioral signal. It says nothing about pagination, ordering, default limits, permissions/auth, or rate limits for what is presumably a paged feed.

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

Conciseness3/5

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

One clean sentence with no filler and the verb-resource pairing front-loaded. However, brevity here borders on under-specification rather than genuine efficiency.

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?

An undocumented 2-parameter schema, no annotations, and no output schema mean the description must do more than this. An agent still cannot tell which network identifiers are valid, what the default limit is, or what shape the returned posts take.

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%, so both parameters (network, limit) are opaque from the schema alone. The description only loosely gestures at them, implying 'network' selects a target and 'recent' relates to the limit, but gives no formats, allowed values, or defaults.

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?

States a specific verb (Read) and resource (recent posts/messages) scoped to a network, so the agent knows this is a feed-read operation. It does not differentiate itself from siblings such as social_queue or social_ledger, and 'a network' is left ambiguous despite a social_networks sibling existing.

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?

No when-to-use or when-not-to-use guidance is given; there is no mention of alternatives or prerequisites. The word 'recent' faintly implies a recency window but nothing tells the agent how this differs from other social_* read/post 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