Skip to main content
Glama

XCROP X (Twitter) data

Check a follow

check_follow
Read-only

Does one X account follow another? Returns both directions. Costs 50 credits.

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": {
      "source": "<source>",
      "target": "<target>"
    },
    "name": "check_follow"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceYesThe account that should be following
targetYesThe account that should be followed

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already cover safety (readOnlyHint=true) and open-world scope, and the description adds two pieces of information the annotations do not: the 50-credit cost and the fact that it returns both directions of the relationship. It says nothing about rate limiting, failure cases for nonexistent accounts, or the exact return shape.

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?

Three short sentences with zero padding, front-loading the core question before the output note and the cost. Every sentence carries information an agent needs.

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 two-parameter read with no output schema, 'returns both directions' is a thin account of the return value and the description says nothing about missing or suspended accounts. The credit cost disclosure offsets this somewhat, but the return contract remains underspecified.

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% and the schema already spells out source and target semantics, so the description adds little beyond the word 'follow' itself. Baseline 3 applies when the schema does the heavy lifting.

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 names a specific verb and resource: it checks whether one X account follows another, pairwise. That clearly separates it from list-oriented siblings like get_followers and get_following, though it never names an alternative explicitly.

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?

'Does one X account follow another?' implies the pairwise verification use case, but the description never says when to prefer this over get_following or get_followers, and it states no exclusions or prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources