Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

mastodon_profile

Look up a public fediverse account profile from a user@instance handle and optionally return cached results to avoid extra credits.

Instructions

mastodon: Look up a fediverse account. GET /v1/mastodon/profile. Looks up acct (user@instance) on that instance's public API. No application token. 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": {
      "acct": "<acct>"
    },
    "name": "mastodon_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
acctYesAccount in the form user@instance.
cache_max_ageNoServe a cached response when it is newer than this. A cache hit costs 0 credits.

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 present, the description carries the full disclosure burden and does well: it declares no application token is required, prices successful calls at 1 credit, and explicitly says errors, blocked/timed-out, invalid requests and cache hits are free. It stops short of covering rate limits or the shape/size of a successful response.

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 front-loaded, which is good, but roughly half the text is a repetitive pricing disclaimer ('Costs 1 credit... cost nothing... charged only where that operation's published cost says so') that restates the same idea three times. The final sentence about not-found charges is vague and adds little actionable information.

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 simple two-parameter read tool, the description covers auth, pricing and caching, which is most of what an agent needs. Because there is no output schema, it should also say what a successful profile response contains, and that gap leaves the definition only minimally 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 description coverage is 100%, so both parameters are already documented. The description adds a little meaning by tying acct to 'user@instance' on that instance's public API and by reiterating that cache_max_age hits cost 0 credits, but nothing beyond the schema about format or behavior.

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 states a specific verb and resource ('Look up a fediverse account') plus the underlying endpoint GET /v1/mastodon/profile, so an agent knows exactly what it does. The platform is clear from the name and the acct format, but there is no explicit statement contrasting it with the many sibling profile lookups (twitter_profile, bluesky_profile, etc.), which keeps it 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?

The cost/credit rules ('Costs 1 credit when it succeeds', cache hits free) give useful decision context, and 'No application token' removes a prerequisite concern. However, there is no explicit when-to-use or when-not-to-use guidance and no named alternative to route to, so usage is only implied.

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