Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

bluesky_profile

Retrieve Bluesky profile details by handle or user ID to inspect public account information through the Fetchproof API.

Instructions

bluesky: Profile. GET /v1/bluesky/profile. Provide one of: handle, user_id. Get Bluesky profile info 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": "bluesky_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleYesBluesky handle

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/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 burden, and it does disclose a real behavioral trait: the credit-cost model, including that errors, blocked/timeout, invalid requests and cache hits are free. That is genuinely useful, but it says nothing about auth requirements, rate limits, or what a successful profile response contains.

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?

"bluesky: Profile. GET /v1/bluesky/profile." largely restates the tool name, and the cost paragraph is long boilerplate that could be compressed to one clause. The input hint does arrive before the billing text, so the useful content is reasonably front-loaded.

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 description covers input and billing but omits the return payload and any failure semantics beyond cost. It is adequate to call the tool, but not complete.

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% for the single parameter, so the baseline is 3. The description's "one of: handle, user_id" adds a small amount of framing but conflicts with the schema, which requires handle, exposes no user_id property, and sets additionalProperties: false.

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?

"Get Bluesky profile info" is a specific verb+resource, and the endpoint line (GET /v1/bluesky/profile) pins down exactly what is retrieved. The platform prefix in the name plus the description make it distinguishable from the other *_profile siblings, though the description never says so explicitly.

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 only guidance is an input constraint ("Provide one of: handle, user_id"), which is really a parameter note rather than a when-to-use rule. Nothing tells the agent when this profile lookup is preferable to, say, bluesky_user_posts or a non-Bluesky profile tool.

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