Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

cosmos_profile

Fetch a public Cosmos profile by handle to view its bio, links, and follower counts.

Instructions

cosmos: Profile. GET /v1/cosmos/profile. Get a public Cosmos profile with bio, links, and follower counts. 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": {
      "handle": "<handle>"
    },
    "name": "cosmos_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
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 no annotations, the description carries the full disclosure burden and does well on cost: 1 credit on success, free on errors, blocked/timed-out and invalid requests, free on cache hits, and conditional charging for not-found/empty results. It still omits auth requirements, rate limits, and whether profiles can be private, so it isn't complete.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded in the first sentence, the route follows, and the remaining sentences cover cost edge cases only. No filler or repetition that doesn't inform a caller.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-param read tool with no output schema, the definition supplies purpose, response contents, and full billing semantics. The main gap is the absence of any statement about authentication or error/empty-result 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?

Only one parameter, and the schema already documents it at 100% coverage ('Cosmos username without a profile URL'). The description adds no further meaning about handle format, casing, or URL stripping 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 profile') and enumerates the returned data (bio, links, follower counts), plus the underlying route GET /v1/cosmos/profile. It does not explicitly distinguish itself from siblings such as cosmos_user_posts or cosmos_cluster, but the resource focus is unambiguous.

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?

There is no guidance on when to choose this profile lookup over sibling tools (posts, clusters, other platforms' profile tools) and no prerequisites stated. The only conditional content is billing behavior, which is not usage guidance.

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