Skip to main content
Glama
Sign In
fanfou-mcp

fanfou-mcp

by Anthonyeef
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_context

Retrieve the reply chain and conversation context for a Fanfou status by its status ID.

Instructions

Get the conversation context (reply chain) of a status.

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": {
      "status_id": "<status_id>"
    },
    "name": "get_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
status_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. 'Get' implies a read-only operation, but nothing is said about ordering, reply depth, pagination, or authentication requirements for the reply chain.

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

Conciseness4/5

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

A single compact sentence with no filler, and the scoping detail '(reply chain)' is front-loaded. It is arguably under-specified rather than verbose, but it wastes no words.

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?

An output schema exists, so return-value shape need not be explained, and the tool has only one parameter. However, with no annotations the description should say more about the reply-chain semantics (depth, ordering, pagination) to be fully callable.

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

Parameters2/5

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

Schema description coverage is 0% for the single required parameter status_id. The description only indirectly implies that the parameter identifies 'a status' and adds no format or source detail to compensate for the empty schema description.

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 (Get) and resource (the conversation context / reply chain of a status), and the parenthetical '(reply chain)' disambiguates it from the sibling get_status, which retrieves the status itself. It is clear without opening the schema, though it never names the sibling it differs from.

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 when-to-use guidance and no mention of alternatives such as get_status or the various timeline tools. The agent must infer that this is for expanding a thread rather than fetching a single status.

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