PR-CY MCP

diff_artifact

Получить diff двух ревизий артефакта.

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": {
      "artifact_id": "<artifact_id>",
      "from_revision_id": "<from_revision_id>"
    },
    "name": "diff_artifact"
  }
}

Input Schema

Name	Required	Description
`artifact_id`	Yes	Идентификатор артефакта.
`to_revision_id`	No	Идентификатор конечной ревизии. None — активная ревизия.
`from_revision_id`	Yes	Идентификатор исходной ревизии.

Output Schema

Name	Required	Description
`diff`	Yes	Unified diff между ревизиями
`is_equal`	Yes	Одинаково ли содержимое сравниваемых ревизий
`to_revision`	Yes	Конечная ревизия
`from_revision`	Yes	Исходная ревизия

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 28, 2026

TDQS

C2.9/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 does not state that this is a read-only operation, what happens if a revision id is invalid, or how large diffs are returned. Only the minimal semantics of a diff are implied.

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?

A single front-loaded sentence with no waste. It is appropriately terse but borders on under-specification given the lack of behavioral context.

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

Completeness3/5

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

The existence of an output schema means return values need not be explained, and the parameters are fully documented. However, for a tool with no annotations and no usage guidance, the description leaves an agent without behavioral or selection context.

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%, including the useful note that to_revision_id=None means the active revision. The description adds nothing beyond the schema, which is the baseline 3 when the schema already documents everything.

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?

States a specific verb+resource: get the diff between two revisions of an artifact. This is clearly distinguishable from siblings like read_artifact or list_artifact_revisions. It does not explicitly name alternatives, so it stops short of 5.

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?

There is no guidance on when to use this versus reading the artifact, listing revisions, or validating it. The agent must infer the use case entirely from the one-line purpose.

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

All PR-CY MCP tools Inspect

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

Need Help?