Skip to main content
Glama

Verify leased premises before acting

verify_premises
Read-only

Stage 2 of the pre-action guard. Re-checks the leases from check_premises against the live record and returns allow only when every one still holds, deny when the record now says the action must not proceed (a decision was closed), and hold otherwise. Catches a record that MOVED while you were preparing — compared by version, so an A to B back to A revision is still detected. Call this immediately before the external action, not earlier. Fails closed on expiry, version movement, a changed intended action, a bad signature or an unreadable record.

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": {
      "intended_action": "<intended_action>",
      "leases": "<leases>"
    },
    "name": "verify_premises"
  }
}

Input Schema

NameRequiredDescriptionDefault
runNoOptional: the SAME run context passed to check_premises. A run that is no longer active is refused.
leasesYesThe leases to re-verify immediately before acting.
action_fieldsNoOptional: the SAME action_fields passed to check_premises. Every lease is bound to the details it was checked with; any detail added, dropped or changed fails closed with fields_mismatch and nothing is consumed.
intended_actionYesMust be the SAME string passed to check_premises. A mismatch fails closed with action_mismatch.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / action_fields
      Added value: +{
      +  "additionalProperties": {
      +    "anyOf": [
      +      {
      +        "type": "string"
      +      },
      +      {
      +        "type": "number"
      +      },
      +      {
      +        "type": "boolean"
      +      },
      +      {
      +        "items": {
      +          "type": "string"
      +        },
      +        "type": "array"
      +      }
      +    ]
      +  },
      +  "description": "Optional: the SAME action_fields passed to check_premises. Every lease is bound to the details it was checked with; any detail added, dropped or changed fails closed with fields_mismatch and nothing is consumed.",
      +  "propertyNames": {
      +    "type": "string"
      +  },
      +  "type": "object"
      +}
    • addedInput schema / properties / leases / items / properties / relied_on
      Added value: +{
      +  "description": "The SAME resources passed to check_premises for this role. Rithmo re-resolves them and rejects the lease if the set differs or any resource is no longer current — this is what makes it impossible to check against one set of resources and act on another.",
      +  "items": {
      +    "properties": {
      +      "content_hash": {
      +        "description": "Optional fingerprint of the EXACT content you consumed from this resource: \"sha256:\" followed by the lowercase hex SHA-256 of its UTF-8 bytes. Not a revision token and not the content itself. When supplied, Rithmo compares it with the content it currently holds for the resource and holds the premise if the resource has changed since you read it (content_check: mismatched) or if it cannot establish the current content (content_check: unverifiable).",
      +        "pattern": "^sha256:[0-9a-f]{64}$",
      +        "type": "string"
      +      },
      +      "provider": {
      +        "description": "The system the resource lives in. Supported: slack, google_drive, github.",
      +        "maxLength": 64,
      +        "minLength": 1,
      +        "type": "string"
      +      },
      +      "resource_id": {
      +        "description": "Provider-native identity of the exact resource, as that system names it — a Slack permalink or \"<channel id>:<message ts>\", a Google Drive file id, \"owner/repo#number\". Never a Rithmo id.",
      +        "maxLength": 512,
      +        "minLength": 1,
      +        "type": "string"
      +      },
      +      "revision_id": {
      +        "description": "Optional provider-native revision/version token for the exact version you read. Recorded as provenance; what it can prove varies by provider and is reported back as revision_assurance.",
      +        "maxLength": 256,
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "provider",
      +      "resource_id"
      +    ],
      +    "type": "object"
      +  },
      +  "maxItems": 8,
      +  "minItems": 1,
      +  "type": "array"
      +}
    • changedInput schema / properties / leases / items / required
      Previous value: -[
      -  "role",
      -  "lease"
      -]New value: +[
      +  "role",
      +  "lease",
      +  "relied_on"
      +]
    • addedInput schema / properties / run
      Added value: +{
      +  "description": "Optional: the SAME run context passed to check_premises. A run that is no longer active is refused.",
      +  "format": "uuid",
      +  "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
      +  "type": "string"
      +}
  2. Added

TDQS

A4.7/5.0
Behavior4/5

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

Adds substantial behavior beyond the annotations: outcome branching (allow/deny/hold), version-based movement detection including the A→B→A case, and a full list of fail-closed conditions (expiry, version movement, changed action, bad signature, unreadable record). The one gap is that the schema implies leases are consumed on success while readOnlyHint=true is asserted; the description does not address that consumption, leaving a mild discrepancy unclarified rather than contradicted.

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?

Five dense sentences, each carrying distinct information: stage identity, outcome semantics, detection mechanism, timing rule, and failure modes. Front-loaded with the stage/relationship, and nothing is repeated from the annotations or schema verbatim.

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?

There is no output schema, and the description compensates by explaining the return vocabulary (allow/deny/hold) and the fail-closed cases. For a nested, guard-style verification tool whose correctness hinges on sequencing and exact input reuse, nothing needed to call it safely 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 goes further by binding parameters to prior calls: the leases must be the same set from check_premises, and intended_action must be the same string (mismatch fails closed with action_mismatch). That identity requirement is the operative semantic an agent could miss from the schema alone.

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?

States a specific verb and resource ('Re-checks the leases from check_premises against the live record') and positions itself as 'Stage 2 of the pre-action guard', so the agent knows exactly which operation this is and how it relates to check_premises. It also enumerates the three possible outcomes (allow/deny/hold), which no sibling name conveys.

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?

Gives an explicit timing rule with an exclusion: 'Call this immediately before the external action, not earlier', and frames the pairing with check_premises as the prerequisite. The when-not (earlier than the action) and the when (immediately before) are both stated plainly.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources