Skip to main content
Glama

Markdown completion log

bpj_markdown_finished_log
Read-onlyIdempotent

Export checked tasks into a plain-text completion log with source lines.

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": {
      "text": "<text>"
    },
    "name": "bpj_markdown_finished_log"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds genuine but modest context: the result is a plain-text log including source lines. It omits what happens when no tasks are checked and how "source lines" are rendered, which matters since no output schema exists.

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?

A single sentence with the verb and the output format front-loaded and no filler. It is arguably slightly too terse for a tool whose input expectations are undefined, but nothing in the sentence is wasted.

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?

The tool is simple (one string parameter, no output schema, safety fully covered by annotations), so a short description is defensible. Still, the agent is left guessing what input format `text` accepts and what the emitted log actually looks like, which for an export tool is the key decision-relevant detail.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Only one parameter exists, so the baseline is 4, and "source lines" plus "checked tasks" does hint that the input is the markdown source containing the task list. However, schema description coverage is 0% and the description never states whether `text` is a whole document or just the task-list lines, nor that the 6000-character cap 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 concrete verb ("Export") and a concrete resource ("checked tasks") plus the output shape ("plain-text completion log with source lines"), so an agent knows this extracts completed task items rather than summarizing or counting them. It does not name a sibling to contrast with, but "checked tasks" implicitly separates it from open-task tools such as bpj_markdown_open_action_list or bpj_markdown_task_progress.

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?

There is no when-to-use or when-not-to-use guidance and no named alternative. An agent must infer from "checked tasks" alone whether this is the right tool versus task-progress or open-action-list siblings, and nothing tells it what precondition (e.g. a task list must exist) applies.

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.