Skip to main content
Glama
Repository Manager

Repository Manager

Generate markdown summary

repository_manager_generate_markdown_summary

Generate a markdown summary of bulk operation results so you can review statuses, output, errors, and metadata in one report.

Instructions

Generates a beautiful markdown summary of bulk operation results.

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": {
      "operation": "<operation>",
      "results": "<results>"
    },
    "name": "repository_manager_generate_markdown_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
resultsYes
operationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv3.6.0
    • removedInput schema / properties / action
      Removed value: -{
      -  "type": "string"
      -}
    • addedInput schema / properties / operation
      Added value: +{
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "action",
      -  "results"
      -]New value: +[
      +  "operation",
      +  "results"
      +]
  2. First observedv3.5.1

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, and destructiveHint=false, so the safety bar is lower. Still, the description does not resolve the meaningful ambiguity these annotations create: whether the summary is returned as a string or written to a file, and whether 'open world' means the tool touches external resources. "Bulk operation results" is the only behavioral hint, and it is thin.

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?

One short, front-loaded sentence with a clear verb, which is the right shape. But "beautiful" is pure filler and the sentence is under-specified rather than genuinely concise.

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?

With no output schema, 2 undocumented required parameters, and a nested results structure, the description should explain the return artifact and the operation argument. It does neither, leaving an agent unable to call the tool correctly without opening the schema.

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%, so the description must carry the load for both required parameters. It gestures at the 'results' array (bulk operation results) but says nothing about the required 'operation' string, what values it accepts, or how status/data/error/metadata fields shape the output. This falls well short of compensating for the coverage gap.

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

Purpose3/5

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

"Generates a markdown summary of bulk operation results" gives a verb and a resource, so the core function is identifiable. However, it does not distinguish this tool from sibling generators such as repository_manager_generate_workspace_template, and the adjective "beautiful" adds no discriminating information.

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?

The description contains no when-to-use guidance, no prerequisites, and no indication of when a caller should pick this generator over the other generate_* sibling. The agent must infer usage entirely from the name.

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