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

@alog-world/mcp

by asicojp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

compile_session

Converts session logs into a structured article ready for publication on the Alog platform.

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": {
      "session_id": "<session_id>"
    },
    "name": "compile_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_idYesコンパイルするセッションID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

C2.9/5.0
Behavior2/5

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

Without annotations, the description carries full burden. It does not disclose side effects (e.g., whether session logs are modified, whether an article is immediately created, or required permissions). The term 'automatically' is vague.

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?

The description is a single, efficient sentence with no redundancy. However, it is too brief and could benefit from a second sentence covering behavior or output.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema or annotations exist. The description does not mention expected output (e.g., article ID) or how the result differs from create_article. Incomplete for a conversion tool.

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?

With 100% schema coverage, the schema already describes the session_id parameter. The description adds no extra meaning beyond the parameter name; 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?

The description explicitly states the conversion action ('compile session logs into articles') and distinguishes the tool from siblings like post_log and create_article. However, it does not clarify whether the resulting article is a draft or published, slightly reducing specificity.

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 compile_session versus create_article or post_log. The description lacks any context about prerequisites or scenario fit.

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