Skip to main content
Glama
Sign In
OpenCOOP MCP Server

OpenCOOP MCP Server

by Pajand
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

check_lock

Determine whether a specific file is currently locked to prevent editing conflicts. Input a file path to get its lock status.

Instructions

Check if a specific file is currently locked.

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": {
      "path": "<path>"
    },
    "name": "check_lock"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesFile path to check

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.11.1

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It doesn't disclose what the return value looks like, whether it returns a boolean or throws an error, whether it follows symlinks, or whether it requires any permissions. For a status-check tool, the return format is important behavioral context.

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?

One short sentence that is front-loaded with the verb and resource. No wasted words.

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?

For a simple one-parameter tool, the description is minimal but lacks return-value information. With no output schema and no annotations, the agent doesn't know what 'check' returns (boolean, status object, error). This is a clear gap for a status-checking 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?

Schema coverage is 100%, so the schema already documents the single parameter. The description adds no additional meaning beyond what the schema provides, 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 states a specific verb ('check') and resource ('a specific file'), and the concept of 'locked' is clear. It doesn't explicitly distinguish from sibling tools like lock_file or unlock_file, but the verb 'check' makes it clear this is a read-only status query rather than a mutation.

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 description implies when to use it: when you need to know if a file is locked. It doesn't explicitly state when not to use it or mention alternatives like list_locks, but the context of sibling tools makes the use case reasonably clear.

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