Skip to main content
Glama
Sign In
Local Grounding MCP

Local Grounding MCP

by archie-ib-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

cleanup_grounding_screenshots

Deletes orphaned grounding screenshots older than a set age, clearing leftover image files and freeing local storage.

Instructions

Delete orphan screenshots.

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

Input Schema

NameRequiredDescriptionDefault
max_age_minutesNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior1/5

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

Since there are no annotations, the description carries the full burden of disclosure. For a destructive action (deletion), it critically fails to warn the user about irreversibility or what 'orphan' status entails.

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?

At only six words, the description is perfectly concise; every word contributes directly to defining the tool's function.

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

Completeness1/5

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

Despite its low complexity, the definition is critically incomplete for a destructive tool, lacking warnings, context on the deletion mechanism, or explanation of how the 'max_age_minutes' parameter actually influences the cleanup scope.

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

Parameters1/5

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

The description adds absolutely no semantic value to the single input parameter 'max_age_minutes' beyond what is implied by the action. The schema coverage is 0%, meaning the description must explain the parameter, which it fails to do.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a clear, specific verb ('Delete') and resource ('orphan screenshots'), immediately distinguishing its purpose from sibling tools like 'load_grounding_model'.

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?

The description provides zero guidance on when to use this cleanup function, offering no context regarding disk space constraints, maintenance schedules, or alternative approaches.

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