Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

cosmos_search

Search public Cosmos posts by keyword to find relevant content, even when an exact match is unavailable. Use the cursor to page through results.

Instructions

cosmos: Search. GET /v1/cosmos/search. Search public Cosmos posts by keyword. Cosmos may return related posts even when there is no exact keyword match. 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": {
      "query": "<query>"
    },
    "name": "cosmos_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesSearch text.
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.5/5.0
Behavior4/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 substantial work: it discloses fuzzy/related-result behavior, precise credit costs per outcome (1 on success, 0 on empty items, 0 on errors/blocked/timeouts/invalid/cache hits), and cursor termination semantics. What remains undisclosed is authorization requirements, rate limiting, page size, and result shape.

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?

The purpose statement is front-loaded and efficient, but the cost block is four clauses long and its final sentence ('A not-found or empty result is charged only where that operation's published cost says so') partially undercuts the earlier flat claim that empty results cost 0 credits, adding ambiguity rather than clarity.

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 two-parameter search tool with no output schema, cost and cursor behavior are covered well, but the description never says what a result contains, how many items a page holds, or what authentication is expected. An agent can call it, but cannot anticipate the response shape.

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%, so both parameters are already documented in-schema, including the unusual 'literal "null" cursor' behavior, and the description does not restate or extend that. Baseline 3 applies since the schema does the semantic heavy lifting.

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: 'Search public Cosmos posts by keyword', plus the underlying route GET /v1/cosmos/search. The word 'public' hints at a scope distinction from author-scoped siblings, but no sibling is named, so the agent must infer that cosmos_user_posts or cosmos_cluster_posts cover narrower scopes.

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 rather than stated: it says it searches by keyword and warns that related posts may come back without an exact match, which is useful context for query design. There is no explicit when-to-use/when-not guidance, no mention of when to prefer cosmos_user_posts or cosmos_cluster_posts, and no stated prerequisites.

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