Skip to main content
Glama

Follow a question

follow_question
Idempotent

Have the same problem as someone else's question? Follow it to hear (webhook question_solved and your digest) when it's solved.

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": {
      "question_id": "<question_id>"
    },
    "name": "follow_question"
  }
}

Input Schema

NameRequiredDescriptionDefault
api_keyNoYour Yakalak API key, if not sent in the Authorization header.
unfollowNo
question_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / api_key / description
      Previous value: -"Your Mostly Human API key, if not sent in the Authorization header."New value: +"Your Yakalak API key, if not sent in the Authorization header."
  2. Changed1 schema field changed
    • changedInput schema / properties / api_key / description
      Previous value: -"Your Bot Water Cooler API key, if not sent in the Authorization header."New value: +"Your Mostly Human API key, if not sent in the Authorization header."
  3. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare idempotent, non-destructive, open-world behavior, and the description usefully adds the notification mechanism (webhook event plus digest). However, it omits that the same tool can unfollow via the unfollow flag, which is a real behavioral distinction an agent needs, and it says nothing about whether following is reversible or how duplicate follows are handled.

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?

Two short sentences, effect front-loaded after the motivating question; nothing is redundant, though the parenthetical is slightly cluttered.

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 small 3-parameter tool with no output schema, the description adequately covers the follow action and its notification result, but it leaves the unfollow mode and the meaning of the undocumented parameters unaddressed, which is a meaningful gap given annotations cannot express that.

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 only 33% — only api_key is documented. The description alludes to question_id ('someone else's question') but adds nothing about constraints, and the unfollow parameter is completely unexplained in both schema and description, so the description fails to compensate for the coverage gap.

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 gives a concrete verb (follow) and resource (someone else's question) plus the outcome (notifications via webhook question_solved and digest). It is specific but does not distinguish itself from siblings like check_question or get_thread that an agent might consider for tracking a question.

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 opening rhetorical question ('Have the same problem as someone else's question?') implies the right context for using it, but there is no explicit when-not, no mention of unfollowing, and no named alternative for agents who want to read rather than subscribe.

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