Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

cosmos_cluster

Fetch a public Cosmos collection and its owner, description, cover, counts, and public subcollections using its URL.

Instructions

cosmos: Collection. GET /v1/cosmos/cluster. Get a public Cosmos collection with its owner, description, cover, counts, and public subcollections. Costs 1 credit when it succeeds. 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"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic Cosmos collection URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description must carry the full behavioral burden. It does disclose costing behavior (1 credit on success, free on errors/cache hits/not-found in some cases), which is genuinely useful, but it says nothing about auth requirements, rate limits, or how the 'public subcollections' portion is bounded or paginated.

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 and the credit-cost caveat is compact, but the leading 'cosmos: Collection. GET /v1/cosmos/cluster.' fragments are redundant restatements of name and route that consume space without adding meaning.

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 one-parameter read tool with no output schema and no annotations, the definition covers purpose, return shape in outline, and cost, but leaves gaps an agent would care about: whether non-public URLs error, output structure of subcollections, and any pagination.

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 single 'url' parameter already carries an example and description, so the schema does the work. The description's 'public Cosmos collection URL' restates rather than adds syntax or format constraints beyond the schema.

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 a public Cosmos collection') and enumerates what comes back (owner, description, cover, counts, public subcollections). It does not explicitly distinguish itself from the sibling cosmos_cluster_posts, so an agent must infer that this returns collection metadata rather than its posts.

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?

The word 'public' implies private or unlisted collections are out of scope, which is a useful implicit constraint, but there is no explicit when-to-use guidance and no pointer to cosmos_cluster_posts for retrieving a collection's posts or to cosmos_search for discovery.

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