Skip to main content
Glama
Sign In
scplus-mcp

scplus-mcp

by Cesar514
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

changes

Get a concise git change summary, optionally scoped to a file, for exact changed-file inspection and line-range summaries instead of broader repository search.

Instructions

Return a tiny git change summary, optionally for one file. Use this for exact changed-file inspection and line-range summaries instead of broader repository search.

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": "changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoOptional indexed file path to scope the change summary to one file.
limitNoMaximum number of changed files to render when path is omitted. Default: 20.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.9

TDQS

A4/5.0
Behavior3/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 discloses that the output is a 'tiny' summary with 'line-range summaries,' but doesn't mention side effects, permissions, or behaviors when no path is given (e.g., limit default). This is adequate but not rich.

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?

The description is two sentences with a clear action verb and no fluff. The second sentence provides useful usage guidance without redundancy, and it is front-loaded with the primary action.

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 simple read-only tool with two optional params and no output schema, the description gives purpose and usage, but omits details like default limit behavior and output format. It is adequate but could be more thorough.

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 description coverage is 100%, with both params (path and limit) described in the schema. The description adds only that the file scope is optional, which is already in the schema, so the baseline of 3 applies.

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 'Return a tiny git change summary' with a specific verb and resource, and distinguishes from siblings by noting 'instead of broader repository search.' It also mentions the optional file scoping, making the purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly says 'Use this for exact changed-file inspection and line-range summaries instead of broader repository search,' providing clear usage context and an alternative category. However, it does not name a specific sibling tool, so it stops short of full when/when-not guidance.

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