PR-CY MCP

search_artifact

Найти подстроку в содержимом активной или указанной ревизии артефакта. В meta ответа возвращаются matches — список совпадений со start, end и text, и count — количество совпадений.

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>",
      "search": "<search>"
    },
    "name": "search_artifact"
  }
}

Input Schema

Name	Required	Description
`search`	Yes	Строка поиска.
`artifact_id`	Yes	Идентификатор артефакта.
`revision_id`	No	Идентификатор ревизии. None — активная ревизия.
`case_sensitive`	No	Учитывать регистр при поиске.

Output Schema

Name	Required	Description	Default
`meta`	No	Дополнительная информация о выполненном действии.
`revision`	Yes	Ревизия артефакта

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 28, 2026

TDQS

A3.6/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 burden. It discloses the return shape (matches with start/end/text plus count), which is useful, but says nothing about permissions, result ordering, empty-match behavior, or that the operation is read-only and non-mutating.

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 tight sentences: the operation is front-loaded and the return contract follows. No filler.

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?

An output schema exists, so the return-value sentence is redundant but harmless; parameters are fully documented in the schema. For a low-risk read tool with no annotations, only the explicit read-only/mutation-free statement is missing.

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%, so baseline is 3. The description reinforces revision_id semantics (active vs specified revision) and the substring nature of search, but adds no syntax, escaping, or matching-rule details beyond the schema.

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 and resource: find a substring in the content of the active or specified artifact revision. This implicitly separates it from read_artifact (full content) and replace_substring_in_artifact (mutation), but no sibling is named explicitly.

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?

The search intent is clear from the verb, and 'active or specified revision' hints at when the revision_id variant applies, but there is no explicit when-to-use guidance or redirect to alternatives such as read_artifact or diff_artifact.

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?