Skip to main content
Glama

Social feed

social_feed

Read APEX Social — the on-chain publishing wall. Returns recent posts with their tip totals. Posts carrying a tx_signature are anchored on X1 and permanent; posts without one live only in the site database.

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

Input Schema

NameRequiredDescriptionDefault
sortNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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, and it does disclose meaningful behavior: posts with a tx_signature are permanent on X1 while those without exist only in the site database. That is genuinely useful durability context. However, it says nothing about read-only guarantees, pagination or result limits, or rate limiting, so transparency is partial.

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?

Two tight sentences that lead with what the tool is and follow with the permanence distinction; nothing is padded or redundant.

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?

No output schema exists, and the description does explain the shape of returned data (posts plus tip totals, and the tx_signature permanence flag). But for a tool with a free-form 'sort' parameter and no annotations, leaving the sort semantics entirely unexplained is a real gap.

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 coverage is 0% and the single parameter 'sort' is undocumented in both the schema and the description. The description gives no hint about accepted sort values or default ordering, so it fails to compensate for the coverage gap.

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 and resource: 'Read APEX Social — the on-chain publishing wall' plus what it returns (recent posts with tip totals). An agent can distinguish it from social_post_how_to, but the description does not explicitly name that sibling or any other feed-like alternative.

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 guidance and no exclusions. The description never says to use social_post_how_to for posting versus this tool for reading, nor when to prefer another feed tool; usage must be inferred from the verb 'Read' alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources