Skip to main content
Glama
Sign In
MisarBlog MCP Server

MisarBlog MCP Server

by Misar-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Follow status

get_follow_status
Read-onlyIdempotent

Check whether a profile is followed and get its follower count using the profile UUID. Requires an API key and counts against your request quota.

Instructions

Get follow status and follower count for a profile UUID. Requires an API key; counts against your plan's request quota.

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": "get_follow_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idYesUUID of the profile to check follow status for

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv5.2.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / user_id / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  2. Changed1 schema field changedv5.1.3
    • changedInput schema / properties / user_id / description
      Previous value: -"UUID of the profile to check, as returned in author fields by article tools. Not the username."New value: +"UUID of the profile to check follow status for"
  3. Changed1 schema field changedv5.1.0
    • changedInput schema / properties / user_id / description
      Previous value: -"UUID of the profile to check follow status for"New value: +"UUID of the profile to check, as returned in author fields by article tools. Not the username."
  4. First observedv2.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description earns credit beyond that by disclosing the authentication requirement and that the call consumes plan quota — real operational cost information an agent cannot get from annotations.

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 filler, with the resource and return contents front-loaded before the operational caveat. Nothing could be removed without losing information.

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 one-parameter read with no output schema, the description usefully names the returned fields (status and follower count) and the auth/quota cost. The only residual ambiguity is whose perspective the 'follow status' reflects (presumably the authenticated account), which is not spelled out.

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% and the single parameter is fully documented with type, UUID format and regex pattern. The description's phrase 'for a profile UUID' merely restates the schema, adding no new syntax or constraint detail, so baseline 3 applies.

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?

States a specific verb and resource ('Get follow status and follower count') plus the scoping key ('for a profile UUID'), so the agent knows exactly what data comes back. It does not name a sibling (e.g. get_profile) or explain how it differs from them, 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?

Usage is only implied by the resource and the UUID requirement; there is no explicit statement of when to call this instead of get_profile or get_reputation, nor any exclusions. The API-key/quota sentence is operational context rather than routing guidance.

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