Skip to main content
Glama

Organize with AI (OwAI)

Inspect device recovery activity

inspect_activity
Read-onlyIdempotent

Read a bounded recovery journal page. A source_id/source_name selects that source's owner; otherwise a device-bound connection inspects its current computer, or an unbound single-owner library is inferred. Local filesystem recovery history needs the owning app online and may include purge_after, purged_at, and cleanup_deferred; purged files cannot be restored. OneDrive cloud-owned organization history is served on the server; provider files follow Microsoft's recycle-bin policy. Pending is not an empty result.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "inspect_activity"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
source_idNo
source_nameNo

Output Schema

NameRequiredDescriptionDefault
commandYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed15 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / device_id
      Removed value: -{
      -  "minLength": 1,
      -  "type": "string"
      -}
    • addedInput schema / properties / source_id
      Added value: +{
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / properties / source_name
      Added value: +{
      +  "maxLength": 200,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • removedInput schema / required
      Removed value: -[
      -  "device_id"
      -]
    • addedOutput schema / properties / command / properties / attempt / maximum
      Added value: +9007199254740991
    • addedOutput schema / properties / command / properties / attempt / minimum
      Added value: +0
    • changedOutput schema / properties / command / properties / attempt / type
      Previous value: -"number"New value: +"integer"
    • addedOutput schema / properties / command / properties / claimed_at / anyOf
      Added value: +[
      +  {
      +    "maximum": 9007199254740991,
      +    "minimum": 0,
      +    "type": "integer"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / command / properties / claimed_at / type
      Removed value: -[
      -  "number",
      -  "null"
      -]
    • addedOutput schema / properties / command / properties / completed_at / anyOf
      Added value: +[
      +  {
      +    "maximum": 9007199254740991,
      +    "minimum": 0,
      +    "type": "integer"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / command / properties / completed_at / type
      Removed value: -[
      -  "number",
      -  "null"
      -]
    • addedOutput schema / properties / command / properties / requested_at / maximum
      Added value: +9007199254740991
    • addedOutput schema / properties / command / properties / requested_at / minimum
      Added value: +0
    • changedOutput schema / properties / command / properties / requested_at / type
      Previous value: -"number"New value: +"integer"
  2. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent/non-destructive annotations: it discloses that local filesystem history requires the owning app online, that results may include purge_after/purged_at/cleanup_deferred, that purged files cannot be restored, that OneDrive cloud history follows Microsoft's recycle-bin policy, and that 'Pending is not an empty result'. These are exactly the operational traits annotations cannot carry.

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?

Front-loaded with the core action in the first sentence, then layered source-selection and provider-behavior details. Sentences are dense but each adds distinct information; the closing 'Pending is not an empty result' is terse yet earns its place as a caller warning.

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?

Output schema exists, so return values need no explanation, and annotations cover the safety profile. The description supplies source-resolution, provider-policy, and purge semantics for a fairly complex read tool, with pagination parameter meaning the main remaining gap.

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 0%, so the description carries the full burden. It explains source_id/source_name resolution semantics well, but limit and offset are only obliquely implied by 'bounded ... page' and never defined, leaving two of four parameters undocumented in both schema and description.

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?

States a specific verb and resource: 'Read a bounded recovery journal page', tied to device recovery activity through the title. An agent can tell this is a read of recovery-history records, distinct from inspect_duplicates or inspect_library. However, it never names or compares against siblings like restore_media or preview_media_deletion, so differentiation is implicit rather than explicit.

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

Usage Guidelines3/5

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

The description explains how source selection resolves (source_id/source_name vs device-bound vs unbound library), which implies when certain modes apply, but gives no explicit when-to-use or when-not-to-use guidance relative to alternatives such as restore_media or inspect_library. Usage must be inferred from the read-only framing.

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