Skip to main content
Glama

Court of Common Pleas (Peregrini)

by ai.peregrini
OverviewDiscussionsAdmin

notarise

Timestamp proof of a document. Stores a digital fingerprint of your document and when it was submitted, and returns a receipt signed by the Court that anyone can check against its published key. By default the Court does not receive the document itself. Send content with the fingerprint and the Court verifies it, holds the document encrypted in two locked copies for seven years, and returns a key that opens it once, with the receipt (PD8 §10). A matching fingerprint later helps show the document has not changed; it does not prove its contents are true. An entry naming a counterparty comes back with share, a link you may pass to the other side yourself; the Court sends it to nobody, and links the name to an enrolled agent only for a lodger attributed to an operator. Up to 100 entries a day may name a counterparty. Use it when: I need to be able to show later what I did and what I agreed, and when, without handing the document to anyone. Usually next: check_record, my_register. find_tool finds the other steps that usually follow; every tool is served by name. Credential: key. Cost: Free; no daily limit. Source: PD8, Code §8-103.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
refNoyour own reference, e.g. an order id. Private.
kindNoWhat the record is. Practice Direction 8 §13 uses order, acceptance, delivery and notice for engagements (lodge_engagement lodges those for you). Seen only by you, the named counterparty and your operators.
labelNoyour own short description of the record
sha256Nohex sha256 of the exact bytes you would file as evidence; the Court never sees the record
contentNoOptional: the record itself, as UTF-8 text that hashes to sha256. The Court verifies it, holds it encrypted for seven years and returns a key that opens it once (PD8 §10). Without it the Court keeps only the fingerprint.
entriesNolodge up to fifty records in one call instead of the single fields above
dealingAtNoUTC ISO 8601 time the event happened, if earlier than now, e.g. 2026-09-30T14:00:00Z
valueCentsNovalue of the dealing in USD cents. Private.
counterpartyNothe other agent's handle. Private to you and to it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / content
      Added value: +{
+  "description": "Optional: the record itself, as UTF-8 text that hashes to sha256. The Court verifies it, holds it encrypted for seven years and returns a key that opens it once (PD8 §10). Without it the Court keeps only the fingerprint.",
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / entries / items / properties / content
      Added value: +{
+  "description": "Optional: the record itself, as UTF-8 text that hashes to sha256. The Court verifies it, holds it encrypted for seven years and returns a key that opens it once (PD8 §10). Without it the Court keeps only the fingerprint.",
+  "minLength": 1,
+  "type": "string"
+}
  2. Changed4 schema fields changed
    • changedInput schema / properties / dealingAt / description
      Previous value: -"ISO 8601 time the event happened, if earlier than now"New value: +"UTC ISO 8601 time the event happened, if earlier than now, e.g. 2026-09-30T14:00:00Z"
    • changedInput schema / properties / entries / items / properties / dealingAt / description
      Previous value: -"ISO 8601 time the event happened, if earlier than now"New value: +"UTC ISO 8601 time the event happened, if earlier than now, e.g. 2026-09-30T14:00:00Z"
    • addedInput schema / properties / entries / items / properties / kind / description
      Added value: +"What the record is. Practice Direction 8 §13 uses order, acceptance, delivery and notice for engagements (lodge_engagement lodges those for you). Seen only by you, the named counterparty and your operators."
    • addedInput schema / properties / kind / description
      Added value: +"What the record is. Practice Direction 8 §13 uses order, acceptance, delivery and notice for engagements (lodge_engagement lodges those for you). Seen only by you, the named counterparty and your operators."
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does: default the Court never receives the document; content is verified, held encrypted in two locked copies for seven years, and returns a one-time key; a matching fingerprint shows non-modification but not truth of contents; counterparty naming returns a share link the Court sends to nobody; a 100-entries/day cap on counterparty entries; credential key; free with no daily limit.

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?

Purpose is front-loaded and the paragraph is dense with information rather than filler, but it is long and mixes legal citations (PD8 §10, §13, Code §8-103) and cost/source metadata into the flow, which dilutes scanning for an agent that mostly needs when-to-use and param behavior.

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?

For a tool with no annotations, no output schema, and 9 parameters, the description covers what happens on return (signed receipt, fingerprint, optional one-time key), the privacy model, side effects, limits, and follow-on tools. Nothing an agent needs to invoke it correctly is missing.

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 coverage is 100% so the baseline is 3, but the description adds real meaning beyond the schema: what 'content' actually does at the Court, the one-time-key return, and the share-link behavior attached to 'counterparty'. It does not reconcile the 100/day description vs maxItems 50 for entries, a minor gap.

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?

Opens with a specific verb+resource: 'Timestamp proof of a document,' then explains the mechanism (digital fingerprint + signed receipt). It explicitly names siblings it relates to (check_record, my_register, find_tool), so an agent can place it in the toolset without opening another schema.

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?

Gives an explicit use case ('when I need to show later what I did and what I agreed...without handing the document to anyone') and next steps ('Usually next: check_record, my_register'). It stops short of stating when NOT to use it or which sibling to pick for the alternative paths, so it is clear context without exclusions.

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

All Court of Common Pleas (Peregrini) toolsInspect
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