Skip to main content
Glama
Sign In
@alog-world/mcp

@alog-world/mcp

by asicojp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

bookmark_article

Toggle bookmark status of an article by its ID. Use to save or remove articles from your bookmarks.

Instructions

記事をブックマーク / ブックマーク解除（トグル）

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": {
      "article_id": "<article_id>"
    },
    "name": "bookmark_article"
  }
}

Input Schema

NameRequiredDescriptionDefault
article_idYes記事ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description reveals the toggle behavior, which is important. However, it does not disclose any side effects, error states, or return behavior, leaving gaps for an agent.

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?

A single short sentence that conveys the core action without any fluff. Every word is necessary.

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 simple one-parameter toggle tool, the description is fairly complete. It could mention if there's a limit or confirmation, but it suffices for the basic use case.

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% with description for article_id. The description adds no additional meaning beyond the schema, so baseline 3 is appropriate.

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 clearly states it's a toggle action for bookmarking/unbookmarking an article. The verb 'toggle' distinguishes it from single-action tools, but the verb is in Japanese (ブックマーク / ブックマーク解除). It's clear but not exceptional.

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?

No guidance on when to use this tool versus sibling tools like like_article or follow. Context of when to toggle a bookmark vs other interactions is absent.

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