Skip to main content
Glama
Sign In
Jarvis Markdown MCP

Jarvis Markdown MCP

by ash25082003
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

finish_work

End a work session by marking it as completed, partial, or blocked, with a summary and optional remaining tasks.

Instructions

Finish the current work session as completed, partial, or blocked.

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": {
      "status": "<status>",
      "summary": "<summary>"
    },
    "name": "finish_work"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusYes
summaryYes
remainingNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations provided, so the description must fully disclose behavior. It only says 'finish' but doesn't explain side effects (e.g., session end, state changes), permissions, or reversibility.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, but it lacks crucial details. It is concise but at the expense of completeness, making it barely adequate.

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?

Given three parameters, no output schema, and no annotations, the description fails to provide enough context. It omits the return value and the effect of finishing a session.

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?

With 0% schema description coverage, the description should add meaning. It mentions status but doesn't explain the enum values, summary, or remaining fields beyond what the schema states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('finish') and the resource ('current work session'), and specifies the possible statuses (completed, partial, blocked), distinguishing it from siblings like start_work or log_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?

No guidance on when to use this tool versus alternatives like log_progress or complete_reminder. No prerequisites or exclusions mentioned.

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