Skip to main content
Glama
Sign In
reposynapse

reposynapse

by Jul879n
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

generate_project_docs

Regenerate .reposynapse/ project docs to keep codebase context current and accurate for AI assistants.

Instructions

Regenerate .reposynapse/ docs. Usually automatic.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "generate_project_docs"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.10.0

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations, the description must carry the behavioral disclosure burden. It discloses that the tool regenerates docs and is normally automatic, but it does not state whether the operation is destructive, what files are touched beyond '.reposynapse/', whether it can be safely rerun, or what it returns.

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?

Two short sentences each carry useful information: the action/resource and the automaticity caveat. There is no filler, and the key action is front-loaded.

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

Completeness4/5

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

For a zero-parameter tool with no output schema, the description is nearly sufficient: it names the target and gives an important usage caveat. It could be slightly more explicit about the effect of calling it manually, but nothing critical is missing for an agent to invoke it.

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?

The schema has zero parameters and 100% coverage vacuously, so there is no parameter semantics burden on the description. The baseline of 4 applies because there are no parameters whose meaning needs explanation.

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 names a specific verb ('Regenerate') and a specific resource ('.reposynapse/ docs'), so an agent can tell this is a documentation-generation action. It doesn't explicitly differentiate from siblings like 'annotate' or 'get_project_context', but the resource target makes the purpose reasonably clear.

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?

'Usually automatic' implies the agent should only call this when automatic regeneration hasn't happened, giving some usage context. However, it stops short of stating explicit when-to-use or when-not-to-use conditions or naming alternatives, so guidance is mostly implied.

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