Skip to main content
Glama

Yardstick ATS

Restore an archived application

yardstick_applications_unarchive
DestructiveIdempotent

Restore one archived application so its status and stage can change again. Changes no status, stage or email.

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": {
      "application_id": "<application_id>"
    },
    "name": "yardstick_applications_unarchive"
  }
}

Input Schema

NameRequiredDescriptionDefault
request_idNo
application_idYes
idempotency_keyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

The annotations already declare destructiveHint=true and idempotentHint=true, so the description's added value is the clarification that the restore itself changes no status, stage or email — i.e., it only removes the archived lock, not any data. This resolves the ambiguity an agent would otherwise have given the destructive hint, and it does not contradict the annotations.

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?

Two short sentences, front-loaded with the action then the scope-limiting clarification. No wasted words, though the second sentence is terse enough that a slightly fuller statement of the parameter surface would have been worth the extra length.

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 simple single-resource mutation this covers effect and side-effect boundaries well, and annotations supply the safety/idempotency profile. However, with three undocumented parameters and no output schema, the definition leaves the agent guessing about how to supply request_id and idempotency_key correctly.

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

Parameters2/5

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

Three parameters exist with 0% schema description coverage, so the description carries the full burden — yet it never mentions application_id, request_id, or idempotency_key. In particular, agents get no explanation of the request/idempotency parameters, which are non-obvious on a tool already marked idempotent by its annotations.

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 names a specific verb and resource ("Restore one archived application") and states the operational effect (status and stage can change again). It is clearly the inverse of an archive operation, though it does not explicitly name the archive sibling for the agent to route away from.

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?

Usage is implied: use this when an application is archived but needs to become transitionable again. There is no explicit when-not guidance, no prerequisites (e.g., permissions), and no named alternative such as a bind vs. direct transition tool for agents who actually want to change status rather than merely restore.

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.