Skip to main content
Glama

Playbook

by com.playbook
OverviewDiscussionsAdmin

Update asset status

update_asset_status
DestructiveIdempotent

Set the status label on an asset (e.g. 'Approved', 'In Review', 'Rejected'). The status value is created on the workspace if it doesn't already exist.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tokenYesAsset token
statusYesStatus label to set
organizationNoWorkspace slug, as returned by list_organizations. Omit it when the account has a single workspace — it is then resolved from your token. Pass it only when the account has several, or when you mean a workspace other than the obvious one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / context
      Removed value: -{
-  "description": "Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): \"Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization.\"",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "token",
-  "status",
-  "context"
-]New value: +[
+  "token",
+  "status"
+]
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly=false, destructive=true, idempotent=true, so the safety profile is covered. The description adds genuinely new context beyond them: the status label is auto-created on the workspace if absent, which tells the agent this call has workspace-level side effects. It does not state whether an existing asset status is overwritten, which holds it back from a 5.

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?

Two sentences, front-loaded with the action and followed by the one non-obvious behavior. No filler or restated fields.

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?

With annotations covering the destructive/idempotent profile and no output schema to explain, the description supplies what an agent needs: the effect, example values, and the workspace-level creation side effect. Nothing essential is missing for a 3-parameter mutation.

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 would be 3, but the description adds value the schema lacks: concrete example status labels ('Approved', 'In Review', 'Rejected'), which matters because the schema defines no enum for the status field. Token and organization parameters are left to their schema text.

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?

Names a specific verb ('Set') and resource ('status label on an asset'), with example values that make the effect concrete. It is distinguishable from siblings like change_asset_tags and update_asset, though it never explicitly contrasts with the neighboring set_asset_approval.

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?

No when-to-use guidance is given: it never says when to reach for this versus set_asset_approval or update_asset, nor any prerequisites. The only additional sentence covers a side effect, not usage context.

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

All Playbook 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