Skip to main content
Glama
Sign In
Files.com MCP Server

Files.com MCP Server

Official
by Files-com
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Find Automation

Find_Automation
Read-only

Retrieve details of a specific automation by ID to review or manage its settings.

Instructions

Show Automation

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

Input Schema

NameRequiredDescriptionDefault
idNoAutomation ID.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.65

TDQS

D1.9/5.0
Behavior2/5

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

Annotations declare readOnlyHint=true and openWorldHint=false, but the description adds no additional behavioral context. It does not mention behavior for null ID, authentication needs, or rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely short (two words), but it is under-specified rather than concise. It fails to convey essential information, so it does not earn high marks for efficiency.

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?

Given the tool's single optional parameter and many sibling tools, the description is far from complete. It does not explain the tool's behavior, return values, or how it differs from List_Automation.

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

Parameters3/5

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

The input schema has 100% description coverage for the sole parameter 'id' ('Automation ID.'). The description adds no further meaning, so baseline score of 3 is appropriate.

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

Purpose2/5

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

Description 'Show Automation' is vague and almost tautological with the name 'Find Automation'. It does not specify that the tool retrieves a specific automation by ID, nor does it differentiate from sibling tools like List_Automation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No usage guidance provided. There is no indication of when to use Find_Automation versus alternatives like List_Automation or other Find_* tools.

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