Skip to main content
Glama
Sign In
viridis-agent-fleet

viridis-agent-fleet

by jdhart81
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

notary__commit

Commit to a deliverable before handover using a commit-reveal scheme. Provides verifiable delivery proofs with idempotent, deadline-bound commitments.

Instructions

[notary — commit-reveal verifiable delivery proofs] Commit to a deliverable BEFORE handover. commit_hash = sha256(salt || sha256(content)) as 64 hex chars; deadline is ISO-8601; context links the escrow/job. Idempotent per (committer, nonce).

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": {
      "committer": "<committer>",
      "nonce": "<nonce>",
      "commit_hash": "<commit_hash>",
      "deadline": "<deadline>"
    },
    "name": "notary__commit"
  }
}

Input Schema

NameRequiredDescriptionDefault
nonceYes
contextNo
deadlineYes
committerYes
commit_hashYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.1.11
    • addedInput schema / properties / commit_hash / title
      Added value: +"Commit Hash"
    • addedInput schema / properties / committer / title
      Added value: +"Committer"
    • addedInput schema / properties / context / title
      Added value: +"Context"
    • addedInput schema / properties / deadline / title
      Added value: +"Deadline"
    • addedInput schema / properties / nonce / title
      Added value: +"Nonce"
    • addedInput schema / title
      Added value: +"commitArguments"
  2. Changed6 schema fields changedv0.1.9
    • removedInput schema / properties / commit_hash / title
      Removed value: -"Commit Hash"
    • removedInput schema / properties / committer / title
      Removed value: -"Committer"
    • removedInput schema / properties / context / title
      Removed value: -"Context"
    • removedInput schema / properties / deadline / title
      Removed value: -"Deadline"
    • removedInput schema / properties / nonce / title
      Removed value: -"Nonce"
    • removedInput schema / title
      Removed value: -"commitArguments"
  3. Changed6 schema fields changed
    • addedInput schema / properties / commit_hash / title
      Added value: +"Commit Hash"
    • addedInput schema / properties / committer / title
      Added value: +"Committer"
    • addedInput schema / properties / context / title
      Added value: +"Context"
    • addedInput schema / properties / deadline / title
      Added value: +"Deadline"
    • addedInput schema / properties / nonce / title
      Added value: +"Nonce"
    • addedInput schema / title
      Added value: +"commitArguments"
  4. Changed6 schema fields changed
    • removedInput schema / properties / commit_hash / title
      Removed value: -"Commit Hash"
    • removedInput schema / properties / committer / title
      Removed value: -"Committer"
    • removedInput schema / properties / context / title
      Removed value: -"Context"
    • removedInput schema / properties / deadline / title
      Removed value: -"Deadline"
    • removedInput schema / properties / nonce / title
      Removed value: -"Nonce"
    • removedInput schema / title
      Removed value: -"commitArguments"
  5. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, description fully covers behavioral traits: explains how commit_hash is computed (sha256 double hash), that deadline is ISO-8601, that context links to escrow/job, and that operation is idempotent. Does not mention potential side effects (e.g., overwrites previous commit?) but for a commit tool this is sufficient.

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?

Three sentences, no fluff. Front-loaded with purpose, then key details (hash computation, deadline, context, idempotency). Every sentence earns its place.

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?

Given no output schema and no annotations, the description adequately explains inputs and effect. Covers all required parameters functionally. Could mention the return value (e.g., commitment ID or status) but not critical since output is likely a simple success indicator.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 0% descriptions; the description compensates by explaining commit_hash format, deadline format, context role, and idempotency via nonce. Not all parameters (e.g., committer) are detailed, but the essence is covered. Adds significant meaning beyond bare property names.

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?

Clearly states the tool's purpose: 'Commit to a deliverable BEFORE handover' as part of a commit-reveal scheme. Uses specific verb 'commit' and resource 'deliverable', distinguishing it from sibling tools like reveal and commitment_status via context.

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?

Explicitly says when to use: before handover. Idempotency hint (per committer, nonce) guides safe usage. Does not list when NOT to use or explicitly name alternatives, but the commit-reveal context makes usage boundary clear.

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