agent-passport-system-mcp

Validate Temporal Rights

validate_temporal_rights

Read-onlyIdempotent

Check a TemporalRights object's validity window, grace period, supersession, and challenge window to determine if rights are active, expired, or superseded.

Instructions

Validate a TemporalRights object by checking its validity window, grace period, supersession, and challenge window.

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": {
      "valid_from": "<valid_from>",
      "valid_until": "<valid_until>"
    },
    "name": "validate_temporal_rights"
  }
}

Input Schema

Name	Required	Description
`valid_from`	Yes	ISO datetime
`grace_until`	No
`valid_until`	Yes	ISO datetime
`effective_at`	No
`superseded_at`	No
`challenge_until`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv4.0.0Aug 1, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

removedInput schema / additionalProperties
```
Removed value: -false
```

Addedv2.8.0May 1, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare a full safety profile (readOnly, idempotent, non-destructive, closed-world), so the description need not restate safety. It adds only the list of validated dimensions. It does not say what a failed validation produces (exception vs. boolean vs. error list), which matters because there is no output schema to fall back on.

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?

A single efficient sentence, front-loaded with the verb and object, with no filler. It is not padded or repetitive. It could have used a second sentence productively for return semantics, but on conciseness alone it is strong.

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

Completeness3/5

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

For a validator with six parameters at 33% schema coverage and no output schema, the description covers the what but not the outcome. It never explains what the caller receives or what happens on invalid input, leaving the result contract entirely unspecified. The annotation set covers safety, but the behavioral contract around validation results 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 coverage is only 33%: valid_from and valid_until are documented as ISO datetimes, while grace_until, effective_at, superseded_at, and challenge_until are undocumented. The description partially compensates by naming the corresponding concepts (grace period, supersession, challenge window), which helps map fields to meaning. It still adds no format or ordering semantics for the bare parameters.

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?

The description gives a specific verb (validate) and resource (TemporalRights object) and enumerates the four aspects checked: validity window, grace period, supersession, and challenge window. This is clear and non-tautological. It does not differentiate itself from siblings, but the sibling list contains no obviously competing validation tool, so the omission is minor.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool, what preconditions must hold, or what alternative to reach for instead. The enumeration of checked fields implies the tool's domain but gives no call-site guidance. An agent cannot tell from the text whether this should be called before or after issuing rights.

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

Deploy Server