Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

cosmos_user_posts

Retrieve public posts saved to a Cosmos user profile by username, with cursor pagination to page through results.

Instructions

cosmos: User Posts. GET /v1/cosmos/user/posts. Get the public posts saved to a Cosmos user profile. 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": {
      "handle": "<handle>"
    },
    "name": "cosmos_user_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
handleYesCosmos username without a profile URL.

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 zero annotations, the description carries the full burden and does deliver the critical non-obvious behavior: a credit is charged only on success, empty results and errors/blocked/timeout/invalid/cache-hit requests cost nothing. It does not disclose return shape, page size, or rate limits, but the cost model is a substantial disclosure the schema does not cover.

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 is front-loaded in the first sentence, with cost semantics after. The cost clauses are somewhat repetitive ("costs nothing"/"costs 0 credits"), but each sentence carries distinct billing information rather than filler.

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?

There is no output schema and no annotations, so the description must cover return content on its own. It says the tool gets public posts but says nothing about the shape of returned items or pagination size, which leaves a gap for a list endpoint.

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 coverage is 100% and both parameters are well documented there, including the unusual cursor rule about sending the literal string "null". The description adds no parameter meaning beyond the schema, so the 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 and resource: "Get the public posts saved to a Cosmos user profile," plus the underlying route. That clearly separates it from cosmos_cluster_posts and cosmos_user_clusters by resource, though it never names a sibling to route away from explicitly.

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 only implied by the resource scope (a user's saved posts). There is no explicit statement of when to prefer this over cosmos_cluster_posts, cosmos_search, or other user-post tools, and no prerequisites or exclusions are given.

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