Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

cosmos_cluster_posts

Fetches public posts saved to a Cosmos collection from a collection URL and supports cursor pagination for paging through results.

Instructions

cosmos: Collection Posts. GET /v1/cosmos/cluster/posts. Get public posts saved to a Cosmos collection. Supports cursor pagination. Costs 1 credit when it succeeds. Costs 0 credits when items is empty. Errors, blocked or timed-out requests, invalid requests and cache hits cost nothing. A not-found or empty result is charged only where that operation's published cost says so.

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": {
      "url": "<url>"
    },
    "name": "cosmos_cluster_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic Cosmos collection URL.
cursorNoPass the previous response cursor unchanged. Stop when it is null; sending the literal string "null" returns an empty terminal page without fetching or charging.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does meaningfully address it: it discloses cursor pagination support and a detailed charging model (1 credit on success, 0 when items is empty, free on errors/blocked/timed-out/invalid/cache hits). It stops short of describing the returned post shape or any rate-limit context, but the cost and pagination disclosure is well beyond the schema.

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?

Purpose and endpoint are front-loaded in the first two sentences, followed by pagination and cost. The cost explanation runs to four sentences with some restatement ('Costs 0 credits' / 'cost nothing'), but each clause conveys a distinct billing case.

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 2-parameter read with no output schema, the description covers invocation, pagination, and billing adequately. The notable gap is that nothing tells an agent what a returned post contains or how to detect a terminal page from the response, which matters because there is no output schema to fall back on.

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 description coverage is 100%, so both url and cursor semantics are already documented, including the unusual 'null' string terminal-page behavior. The description adds only the framing that the collection must be public; baseline 3 applies.

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+resource: 'Get public posts saved to a Cosmos collection', reinforced by the endpoint 'GET /v1/cosmos/cluster/posts'. This is clearly distinguishable from cosmos_user_posts or cosmos_search by the collection scope, though the description never names a sibling to sharpen that contrast.

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

Usage Guidelines3/5

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

Usage is implied only: an agent can infer you call this when you have a public collection URL and want its saved posts. There is no explicit when-to-use, no when-not, and no pointer to cosmos_cluster or cosmos_user_posts for adjacent needs.

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