Skip to main content
Glama

verify_pr_range

Verify signed and unsigned commits across a pull request commit range for merge gates and PR review. Supports hosted and offline verification modes.

Instructions

Scroll Gate: verify signed/unsigned commits across a PR commit range.

Use for merge gates and PR review (many commits). Prefer ``verify_envelope``
for one commit offline. Prefer ``audit_export`` when auditors need bundles,
not pass/fail on a range.

Hosted mode (default): calls ssx360.com; requires SSX360_API_KEY.
Set ``source=local|notes|bundle`` to verify offline without an API key.
Read-only for Git refs; hosted mode emits usage to ssx360.com.
Returns ``{ok, verified_count, unsigned_shas?, failures?, error?}``.

Parameters:
    workspace: Git repo root (defaults to detected repo).
    base: Range start ref (exclusive), e.g. origin/main.
    head: Range end ref (inclusive), e.g. HEAD or PR head SHA.
    source: Envelope transport — hosted, local, notes, or bundle.
    notes_ref: Git notes ref when source=notes.
    bundle_dir: Bundle directory when source=bundle.
    require_mode: Policy require_mode filter.
    trusted_keys_file: Trusted keys JSON for signed/untrusted actor checks.
    require_actor_types / deny_actor_types: Actor policy lists.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
baseNoRange start Git ref (exclusive), typically origin/main.origin/main
headNoRange end Git ref (inclusive), e.g. HEAD or a PR head SHA.HEAD
sourceNoEnvelope transport: hosted Scroll Gate (default, requires SSX360_API_KEY), local files, git notes, or bundle dir for offline verification.hosted
notes_refNoGit notes ref when source=notes, default refs/notes/matrixscroll.refs/notes/matrixscroll
workspaceNoGit repository root. Empty auto-detects from the working directory.
bundle_dirNoDirectory containing exported envelope bundles when source=bundle.
require_modeNoOptional policy require_mode filter applied to every commit in the range.
deny_actor_typesNoOptional deny-list of provenance.actor_type values.
trusted_keys_fileNoOptional JSON file of trusted public keys for the range check.
require_actor_typesNoOptional allow-list of provenance.actor_type values.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

The description adds context beyond annotations, such as the return format, the fact that hosted mode emits usage to ssx360.com, and that it is read-only for Git refs. Annotations already indicate openWorldHint and readOnlyHint, but description elaborates on side effects.

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?

The description is well-structured with sections and front-loaded purpose. It is somewhat long but each sentence adds value. Slight redundancy in parameter listing could be trimmed, but overall effective.

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

Completeness5/5

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

Given the complexity (10 parameters, output schema, multiple usage modes), the description covers all necessary context: when to use, how to use (hosted vs offline, API key), return format, and parameter explanations. The existence of an output schema complements the description.

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 the baseline is 3. The description lists parameters with brief explanations, but does not add significant new meaning beyond what the schema already provides.

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 starts with a specific verb and resource ('verify signed/unsigned commits across a PR commit range') and clearly distinguishes from sibling tools like verify_envelope and audit_export.

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

Usage Guidelines5/5

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

Explicitly states when to use this tool ('merge gates and PR review'), and provides alternatives ('verify_envelope for one commit offline', 'audit_export when auditors need bundles'). Also covers hosted vs offline modes.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SSX360/matrixscroll'

If you have feedback or need assistance with the MCP directory API, please join our Discord server