Skip to main content
Glama

refresh_bins

Refresh media pool folders to pick up collaborator changes and report stale bins.

Instructions

Refresh the media pool folders (picks up changes from collaborators) and report stale bins.

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": "refresh_bins"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=false, so the agent knows this mutates local state without destroying data. The description usefully explains what the refresh accomplishes and that it also reports stale bins, but it does not say whether local edits are affected, whether the operation is idempotent, or what the report contains.

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?

A single sentence that front-loads the action and its purpose, with the secondary 'report stale bins' clause tied on compactly. No filler or redundancy.

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?

For a zero-parameter tool with annotations covering the safety profile, the description gives enough to call it correctly. The only modest gap is that there is no output schema, so the 'report stale bins' result is described only in outline.

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?

The tool takes zero parameters, so there is no parameter meaning for the description to add; baseline 4 applies. Nothing in the description mischaracterizes the empty input schema.

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 ('Refresh') and resource ('media pool folders'), plus the practical effect ('picks up changes from collaborators') and a secondary output ('report stale bins'). It is clear on its own, though it does not explicitly distinguish itself from the similarly named refresh_luts sibling.

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 rather than stated: 'picks up changes from collaborators' hints at the triggering situation, but there is no explicit when-to-use or when-not-to-use guidance and no named alternative among the refresh/delete/create bin siblings.

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

Deploy Server

Other Tools