Skip to main content
Glama
Sign In
fanfou-mcp

fanfou-mcp

by Anthonyeef
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

friendship

Follow or unfollow a Fanfou user with explicit confirmation. Use to control your following list on the Fanfou platform.

Instructions

Follow (action='create') or unfollow (action='destroy') a user. WRITE ACTION: only call after the user has explicitly confirmed this exact action and content in chat. Requires confirm=true.

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": {
      "user_id": "<user_id>"
    },
    "name": "friendship"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionNocreate
confirmNo
user_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations provided, the description carries the full behavioral burden and does disclose the most important trait: this is a write action gated behind explicit confirmation and a confirm=true flag. It stops short of describing side effects on timelines, rate limits, or failure behavior.

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?

Two sentences, zero waste, with the operation mapping and the safety guardrail both front-loaded. Every sentence earns its place.

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 mutation tool with no annotations and no output schema, the description supplies the critical confirmation protocol. Remaining gaps are minor: whether unfollow also requires confirmation, and what a failed or rejected call returns.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate — and it does for the two non-obvious parameters: action ('create'=follow, 'destroy'=unfollow) and confirm (must be true for the write). user_id is self-evident from the name, leaving only minor gaps.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the two specific operations (follow/unfollow) and maps them to the action values, fully disambiguating the opaque name 'friendship'. An agent can distinguish this from siblings like favorite or post_status without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states a clear precondition for use: only call after the user has explicitly confirmed the exact action and content in chat. It doesn't name alternative tools or when-not-to-use cases, but no sibling overlaps with follow/unfollow semantics.

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