Skip to main content
Glama

stat

Read-only

Retrieve a file or folder’s size, permissions, and last modified time to inspect WordPress site files and folders.

Instructions

Size, permissions and modified time of a file or folder.

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": {
      "path": "<path>"
    },
    "name": "stat"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
siteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.2

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description's only added behavioral content is the set of returned attributes; it says nothing about error behavior for nonexistent paths, symlink following, or whether permission data reflects the caller or the file owner.

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?

Nine words, front-loaded, with zero filler — the returned fields lead immediately. The only structural weakness is that it is a fragment lacking a verb, which reads as a label rather than a definition.

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?

With no output schema, the description usefully enumerates the three returned fields, which is the minimum an agent needs to interpret results. But for a 2-parameter tool with zero schema documentation, it is silent on parameter meaning, error conditions, and remote-site behavior, leaving real gaps.

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?

Schema description coverage is 0%, so the description must carry parameter meaning, and it does not. It never explains whether 'path' accepts relative or absolute paths or whether it may point at a folder, nor does it explain the optional 'site' parameter, which appears to select a remote site context and is completely undocumented.

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 the exact attributes retrieved (size, permissions, modified time) for a file or folder, which pins down what the tool does far better than the opaque name 'stat' alone. It is a noun fragment rather than a verb+resource statement, and it does nothing to separate itself from siblings such as read_file or list_dir, so it stops short of a 5.

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?

There is no when-to-use guidance, no statement of when to prefer this over read_file or list_dir, and no mention of prerequisites. The agent must infer the usage context entirely from the returned-field list.

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