Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

cosmos_user_clusters

Retrieve public collections owned by a Cosmos user by handle, using cursor-based pagination to page through results.

Instructions

cosmos: User Collections. GET /v1/cosmos/user/clusters. Get the public collections owned by a Cosmos user. 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_clusters"
  }
}

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

B3.3/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 behavioral burden and does add real value by disclosing a cost model: 1 credit on success, 0 credits on empty results, errors, blocked/timed-out requests, invalid requests, and cache hits. However it omits any statement about auth requirements, result ordering, page size, or what a collection record contains, and the closing sentence ('A not-found or empty result is charged only where that operation's published cost says so') sits in mild tension with the earlier 'Costs 0 credits when items is empty', leaving the agent slightly unsure about the empty-result charge.

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?

Purpose and endpoint are correctly front-loaded, but four of the six sentences are spent on credit accounting, with partial redundancy between 'Costs 0 credits when items is empty' and the final 'not-found or empty result' sentence. The pricing block could be compressed into one or two sentences without losing information, and the ambiguity it introduces costs more than the length saves.

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 should stand in for return-value expectations; it says nothing about what collections look like, their ordering, or how the cursor terminates the listing beyond the schema's note. Purpose and cost are covered, but an agent still has gaps about the shape and completeness of results before calling.

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 the schema already explains both the cursor passthrough convention (including the literal "null" edge case) and that handle is a username without a profile URL. The description adds no parameter-level meaning beyond that, so the baseline of 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?

The description gives a specific verb and resource: 'Get the public collections owned by a Cosmos user', reinforced by the endpoint GET /v1/cosmos/user/clusters. It implicitly separates itself from sibling cosmos_cluster (a single collection) by emphasizing collections owned by a user, but it never names an alternative tool, so differentiation stops short of a 5.

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: an agent can infer it should call this when it has a handle and wants that user's collections. There is no explicit when-to-use statement, no exclusion, and no pointer to cosmos_user_posts or cosmos_cluster for adjacent needs, so the agent must infer routing from the tool name alone.

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