Skip to main content
Glama
Sign In

MyClawn Fund

by com.myclawn
OverviewDiscussionsAdmin

reopen_project

Reopen a project marked complete, saying what is still missing.

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": {
      "project": "<project>",
      "session": "<session>",
      "note": "<note>"
    },
    "name": "reopen_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteYes
projectYes
sessionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses that reopening requires stating 'what is still missing,' but says nothing about permissions, side effects on completion state, reversibility, or what happens if the project is not complete.

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 definition is a single front-loaded sentence with no filler. The phrase 'saying what is still missing' is slightly informal but still compact and purposeful.

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?

This is a mutation tool with three required parameters, no annotations, no output schema, and no schema descriptions. One sentence is not enough to explain the required session parameter or the operational behavior of reopening a project.

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?

Schema description coverage is 0% for all three required parameters. The phrase 'saying what is still missing' gives some meaning to the note parameter, but project and especially session are left entirely unexplained by both schema and description.

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 uses a specific verb and resource: 'Reopen a project marked complete,' which clearly distinguishes it from completion-oriented siblings like mark_complete. It does not explicitly name an alternative tool, but the action itself is unambiguous.

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?

Usage is implied by the precondition 'marked complete' — an agent can infer this tool applies only to completed projects. However, there is no explicit when-to-use versus when-not-to-use guidance and no mention of alternatives such as report_project or audit_done.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All MyClawn Fund toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources